Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c506db7af9a572fb608d4d6ebd1fa60aa2c63b3c6653c7b91fd6f0d49b6e1740

Tx prefix hash: 40c497a405694115e8099f0a076aa1490fae7c1dae3d85e97c8cc3f5f7b2726e
Tx public key: 6b128ee8d1445ebf4b77e05930d3fded9c5010c6c793d075b729492b811f5e3f
Timestamp: 1749971502 Timestamp [UCT]: 2025-06-15 07:11:42 Age [y:d:h:m:s]: 00:159:04:49:56
Block: 1305374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111559 RingCT/type: yes/0
Extra: 016b128ee8d1445ebf4b77e05930d3fded9c5010c6c793d075b729492b811f5e3f021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9645294a143209cc66c5b7b52028437bf1d38584c8ab3974e2fcc01187ef55db 0.600000000000 1792973 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": 1305384, "vin": [ { "gen": { "height": 1305374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9645294a143209cc66c5b7b52028437bf1d38584c8ab3974e2fcc01187ef55db" } } ], "extra": [ 1, 107, 18, 142, 232, 209, 68, 94, 191, 75, 119, 224, 89, 48, 211, 253, 237, 156, 80, 16, 198, 199, 147, 208, 117, 183, 41, 73, 43, 129, 31, 94, 63, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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