Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8efe64ebc3b56048871febb459fc86a05f84da0d572357c70dc5d618a5c4d8f9

Tx prefix hash: 5e04a838dcd34555efe3e9f82a3c629f2c56d1c997ced0b70e00c44821ca019d
Tx public key: 203981233f0cba972572e8d3aae85fa2f7f76c664c55d4562953293c17153e02
Timestamp: 1703222076 Timestamp [UCT]: 2023-12-22 05:14:36 Age [y:d:h:m:s]: 01:322:04:40:35
Block: 918453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489121 RingCT/type: yes/0
Extra: 01203981233f0cba972572e8d3aae85fa2f7f76c664c55d4562953293c17153e020211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 324e4743f6a5ab3a8d57dbb2424ada8e5d0283b5344260e10148b14a14720e21 0.600000000000 1376097 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": 918463, "vin": [ { "gen": { "height": 918453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "324e4743f6a5ab3a8d57dbb2424ada8e5d0283b5344260e10148b14a14720e21" } } ], "extra": [ 1, 32, 57, 129, 35, 63, 12, 186, 151, 37, 114, 232, 211, 170, 232, 95, 162, 247, 247, 108, 102, 76, 85, 212, 86, 41, 83, 41, 60, 23, 21, 62, 2, 2, 17, 0, 0, 0, 7, 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