Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01915e61c6ac8f24cf7599b6a8f9b57e853c516145c710e10d809f7ad982eec8

Tx prefix hash: 33c1fa956345baca48efa557549d5203e995e1180995f03da9f28d666a85b765
Tx public key: 0d2f0ed38af939eca3dd1eb443267892100c6b98d93af413b74d1646cd7cd14a
Timestamp: 1710532308 Timestamp [UCT]: 2024-03-15 19:51:48 Age [y:d:h:m:s]: 00:244:13:01:25
Block: 979079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175057 RingCT/type: yes/0
Extra: 010d2f0ed38af939eca3dd1eb443267892100c6b98d93af413b74d1646cd7cd14a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 371d7ae517f8326da5874b7e7f37c82aef71d7c0b81bb6962637f0a9cc3798e5 0.600000000000 1439110 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": 979089, "vin": [ { "gen": { "height": 979079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "371d7ae517f8326da5874b7e7f37c82aef71d7c0b81bb6962637f0a9cc3798e5" } } ], "extra": [ 1, 13, 47, 14, 211, 138, 249, 57, 236, 163, 221, 30, 180, 67, 38, 120, 146, 16, 12, 107, 152, 217, 58, 244, 19, 183, 77, 22, 70, 205, 124, 209, 74, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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