Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d0a24aff38251378a5677b36dc0042ac5a50f63dd1c12b237b358b501426779

Tx prefix hash: c648ecdae36ab4fd000fd691d8b8a00541b3250f2025a6c925c71f289f8310a7
Tx public key: 007795fa5ac41187c3178f1fcae4ffb9133db8d6a0aab473c81d5b18109a1b15
Timestamp: 1717744104 Timestamp [UCT]: 2024-06-07 07:08:24 Age [y:d:h:m:s]: 00:315:02:49:01
Block: 1038862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225203 RingCT/type: yes/0
Extra: 01007795fa5ac41187c3178f1fcae4ffb9133db8d6a0aab473c81d5b18109a1b150211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdfd3aeeb61d4ebe78e8a8de6eb2ebfe9ded8584b2cf239a861c03dfee1207b4 0.600000000000 1507423 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": 1038872, "vin": [ { "gen": { "height": 1038862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdfd3aeeb61d4ebe78e8a8de6eb2ebfe9ded8584b2cf239a861c03dfee1207b4" } } ], "extra": [ 1, 0, 119, 149, 250, 90, 196, 17, 135, 195, 23, 143, 31, 202, 228, 255, 185, 19, 61, 184, 214, 160, 170, 180, 115, 200, 29, 91, 24, 16, 154, 27, 21, 2, 17, 0, 0, 0, 4, 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