Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1e2b1daf4aa8658cbfaaff8b4030cf3401b3fb7bf74b5461f5c6aa6d63cc1db

Tx prefix hash: 182bc5f4449fc76ff24306950c99b2ee3ebd48a9a4ba25e713e33ba49d590433
Tx public key: 6f2c34e66de5b868039f13d986f2588ba3c8b1bb05da0dde633337fb0de57d8a
Timestamp: 1759206679 Timestamp [UCT]: 2025-09-30 04:31:19 Age [y:d:h:m:s]: 00:007:18:11:00
Block: 1379468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5558 RingCT/type: yes/0
Extra: 016f2c34e66de5b868039f13d986f2588ba3c8b1bb05da0dde633337fb0de57d8a02110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df814d417a857bbc5624ce0e622e6cd0f57441016678dcaad7b49f3bdd51bf1e 0.600000000000 1867565 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": 1379478, "vin": [ { "gen": { "height": 1379468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df814d417a857bbc5624ce0e622e6cd0f57441016678dcaad7b49f3bdd51bf1e" } } ], "extra": [ 1, 111, 44, 52, 230, 109, 229, 184, 104, 3, 159, 19, 217, 134, 242, 88, 139, 163, 200, 177, 187, 5, 218, 13, 222, 99, 51, 55, 251, 13, 229, 125, 138, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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