Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f2ae32e389ae68483715cd108b0f0eab46d4e63e9a2db6ddddffda60cff2095

Tx prefix hash: 938f2375896ebcabf8577618b261f8c3aa1bb1d26f4f026a1b979ecbf92784b2
Tx public key: b60e51687207c71656e25a1647c881d86d8054dfa8d2faf09d8ffbafe43b97ee
Timestamp: 1708080847 Timestamp [UCT]: 2024-02-16 10:54:07 Age [y:d:h:m:s]: 00:331:15:46:10
Block: 958733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237427 RingCT/type: yes/0
Extra: 01b60e51687207c71656e25a1647c881d86d8054dfa8d2faf09d8ffbafe43b97ee0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90b3e90ef10c8132657aab18b32e4691c05e7fb9d5980f732222ab59ef77f22e 0.600000000000 1418094 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": 958743, "vin": [ { "gen": { "height": 958733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90b3e90ef10c8132657aab18b32e4691c05e7fb9d5980f732222ab59ef77f22e" } } ], "extra": [ 1, 182, 14, 81, 104, 114, 7, 199, 22, 86, 226, 90, 22, 71, 200, 129, 216, 109, 128, 84, 223, 168, 210, 250, 240, 157, 143, 251, 175, 228, 59, 151, 238, 2, 17, 0, 0, 0, 1, 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