Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c601e977e4d1c3e4a82a71ca4e16b66be40273d31b95f045d3ed2da6b161488c

Tx prefix hash: 7cc70f9058a1c0eef9de74d46d17bf009035985848279c1e45d760ff79893f29
Tx public key: 344f582433e1c38e8d47aaed2a062b924bb401425dddeddff4fd44139d00014a
Timestamp: 1737729787 Timestamp [UCT]: 2025-01-24 14:43:07 Age [y:d:h:m:s]: 00:173:13:40:47
Block: 1204349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122826 RingCT/type: yes/0
Extra: 01344f582433e1c38e8d47aaed2a062b924bb401425dddeddff4fd44139d00014a0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 205bfe3afc9d201df9e3dccded0d3e6a140a46664560278d1f77b516698ba1a7 0.600000000000 1691034 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": 1204359, "vin": [ { "gen": { "height": 1204349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "205bfe3afc9d201df9e3dccded0d3e6a140a46664560278d1f77b516698ba1a7" } } ], "extra": [ 1, 52, 79, 88, 36, 51, 225, 195, 142, 141, 71, 170, 237, 42, 6, 43, 146, 75, 180, 1, 66, 93, 221, 237, 223, 244, 253, 68, 19, 157, 0, 1, 74, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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