Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59007fd3e7b172638c8dbf220abfcafa9b4a7eca0d035f1281796c0674ba034b

Tx prefix hash: 26060c8f9b0d411414d66c13fb19068cc9a62cd01344c4b89b0182d1275c184c
Tx public key: 02e91532ef4099e196c4009ed9d841812df3096c4c6d20526cc05f3e47ba6d9e
Timestamp: 1710422334 Timestamp [UCT]: 2024-03-14 13:18:54 Age [y:d:h:m:s]: 01:085:18:33:54
Block: 978170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322319 RingCT/type: yes/0
Extra: 0102e91532ef4099e196c4009ed9d841812df3096c4c6d20526cc05f3e47ba6d9e02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06b3c69bc89a9f319db301675e1036128a6fd6fc0aefd07b7645111438263b5c 0.600000000000 1438187 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": 978180, "vin": [ { "gen": { "height": 978170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06b3c69bc89a9f319db301675e1036128a6fd6fc0aefd07b7645111438263b5c" } } ], "extra": [ 1, 2, 233, 21, 50, 239, 64, 153, 225, 150, 196, 0, 158, 217, 216, 65, 129, 45, 243, 9, 108, 76, 109, 32, 82, 108, 192, 95, 62, 71, 186, 109, 158, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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