Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 413c0d598e86e1899b7ce5f57a260cc47ddb97601cf6b3edfa8252ae02c4a61e

Tx prefix hash: e34d3b102a3961846f62db75023dae21ea1b82e2384bb884c7801fa5e9f2d75c
Tx public key: 0c2c6ca6b1d6a8c407c3b4798fe61c92b2a3939ae518b0fb908795cd1f5a4d9d
Timestamp: 1748589063 Timestamp [UCT]: 2025-05-30 07:11:03 Age [y:d:h:m:s]: 00:175:17:15:38
Block: 1294035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123272 RingCT/type: yes/0
Extra: 010c2c6ca6b1d6a8c407c3b4798fe61c92b2a3939ae518b0fb908795cd1f5a4d9d02110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85d84265e2bd6059aeca85027c522bc2a203735c2eb35766ce9cd33a476eec46 0.600000000000 1781530 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1294045, "vin": [ { "gen": { "height": 1294035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85d84265e2bd6059aeca85027c522bc2a203735c2eb35766ce9cd33a476eec46" } } ], "extra": [ 1, 12, 44, 108, 166, 177, 214, 168, 196, 7, 195, 180, 121, 143, 230, 28, 146, 178, 163, 147, 154, 229, 24, 176, 251, 144, 135, 149, 205, 31, 90, 77, 157, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8