Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518f387f9690b0593c848b65334b2d71c59240e1f4a993ca70918f2dfc3c5986

Tx prefix hash: df53e8dc72ea9b2b4e6bdfa7058fdf6c351271d1ed2dc3603eb861d051db0393
Tx public key: 7933f2183add52921f2138f54bf8572322a1048eef81e9daa9ce4942679d37d0
Timestamp: 1752018257 Timestamp [UCT]: 2025-07-08 23:44:17 Age [y:d:h:m:s]: 00:207:11:28:40
Block: 1321627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146660 RingCT/type: yes/0
Extra: 017933f2183add52921f2138f54bf8572322a1048eef81e9daa9ce4942679d37d0021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fe52be2f224f0e12493d0ba5f52f93dfaaecd12d2f50daeaa48478f069df908 0.600000000000 1809334 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": 1321637, "vin": [ { "gen": { "height": 1321627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe52be2f224f0e12493d0ba5f52f93dfaaecd12d2f50daeaa48478f069df908" } } ], "extra": [ 1, 121, 51, 242, 24, 58, 221, 82, 146, 31, 33, 56, 245, 75, 248, 87, 35, 34, 161, 4, 142, 239, 129, 233, 218, 169, 206, 73, 66, 103, 157, 55, 208, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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