Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3601568f25d51e7183b001d6949ca25d4c3a3e7f25ce1c491302f32673446a63

Tx prefix hash: bed1220cf4598f0fdfd202f8b80d576760e2a5f7c47c405e21b5c842b2817bb8
Tx public key: d55e88eb51f5447b9470018d6da8b247f68dadfbc4bb61ad77c3628f46a3d6b4
Timestamp: 1677969740 Timestamp [UCT]: 2023-03-04 22:42:20 Age [y:d:h:m:s]: 01:359:00:33:13
Block: 709986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517270 RingCT/type: yes/0
Extra: 01d55e88eb51f5447b9470018d6da8b247f68dadfbc4bb61ad77c3628f46a3d6b40211000000015029cbac000000000000000000

1 output(s) for total of 2.725973009000 dcy

stealth address amount amount idx
00: d1c776f5ec9fd3a342b6933d5940640a3a853c49d956f0b9454cac495522c995 2.725973009000 1154013 of 0

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": 709996, "vin": [ { "gen": { "height": 709986 } } ], "vout": [ { "amount": 2725973009, "target": { "key": "d1c776f5ec9fd3a342b6933d5940640a3a853c49d956f0b9454cac495522c995" } } ], "extra": [ 1, 213, 94, 136, 235, 81, 245, 68, 123, 148, 112, 1, 141, 109, 168, 178, 71, 246, 141, 173, 251, 196, 187, 97, 173, 119, 195, 98, 143, 70, 163, 214, 180, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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