Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0fa1435065c3a10e71584a7eb4736f9fd86fbaf690f22ce7b5bbe051e60b31d

Tx prefix hash: f34051700b6f41caa3186049aac820a174e07fd58631d64a586252874def6998
Tx public key: f97c3fa8e3ceba6b5db02b144125b94f5c76c4c253de7b5171ae4a214146da86
Timestamp: 1734874048 Timestamp [UCT]: 2024-12-22 13:27:28 Age [y:d:h:m:s]: 00:165:07:47:12
Block: 1180776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117961 RingCT/type: yes/0
Extra: 01f97c3fa8e3ceba6b5db02b144125b94f5c76c4c253de7b5171ae4a214146da86021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d00b2baeccb7ca60e412527eb440f1f79881a85eb069fdb00a156e1069918e04 0.600000000000 1667189 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": 1180786, "vin": [ { "gen": { "height": 1180776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d00b2baeccb7ca60e412527eb440f1f79881a85eb069fdb00a156e1069918e04" } } ], "extra": [ 1, 249, 124, 63, 168, 227, 206, 186, 107, 93, 176, 43, 20, 65, 37, 185, 79, 92, 118, 196, 194, 83, 222, 123, 81, 113, 174, 74, 33, 65, 70, 218, 134, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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