Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9371e5a28d325e6dcd350fc6d6701f817b24c614eb6a51d11e63294e9c562ae

Tx prefix hash: 3b9e08a8c86a8b58cb625a324a88441467d594ad570613f87a1c91fe50f7ebcd
Tx public key: b698dcff19002f728fdee5fa26ef1661b9574f496f8a18c528702fe2af3572c3
Timestamp: 1763014031 Timestamp [UCT]: 2025-11-13 06:07:11 Age [y:d:h:m:s]: 00:055:06:05:47
Block: 1411034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39573 RingCT/type: yes/0
Extra: 01b698dcff19002f728fdee5fa26ef1661b9574f496f8a18c528702fe2af3572c30211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1ee2e5220d6d6e26012f7774a2a56d4b8bd3e4201abf94d0eaaa140c967215f 0.600000000000 1899491 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": 1411044, "vin": [ { "gen": { "height": 1411034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1ee2e5220d6d6e26012f7774a2a56d4b8bd3e4201abf94d0eaaa140c967215f" } } ], "extra": [ 1, 182, 152, 220, 255, 25, 0, 47, 114, 143, 222, 229, 250, 38, 239, 22, 97, 185, 87, 79, 73, 111, 138, 24, 197, 40, 112, 47, 226, 175, 53, 114, 195, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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