Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12331e0cfd40e5507d531a737de5c22a9d0e11d44ddfdd783346a31068e2875d

Tx prefix hash: 9adc7264b7427eafc16b2199e42f1c0d43f0da865f72180bf89e367faef18c32
Tx public key: ea0bd0d15cdb5fe79433e532a3f3ff5be25258ecae3be5a3bdb39294b7542e8f
Timestamp: 1732982693 Timestamp [UCT]: 2024-11-30 16:04:53 Age [y:d:h:m:s]: 00:114:03:01:33
Block: 1165091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81356 RingCT/type: yes/0
Extra: 01ea0bd0d15cdb5fe79433e532a3f3ff5be25258ecae3be5a3bdb39294b7542e8f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d961bc21ef71b44d979bb4b8565115a13e2b752426732d8c8a2718c883500d5 0.600000000000 1650766 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": 1165101, "vin": [ { "gen": { "height": 1165091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d961bc21ef71b44d979bb4b8565115a13e2b752426732d8c8a2718c883500d5" } } ], "extra": [ 1, 234, 11, 208, 209, 92, 219, 95, 231, 148, 51, 229, 50, 163, 243, 255, 91, 226, 82, 88, 236, 174, 59, 229, 163, 189, 179, 146, 148, 183, 84, 46, 143, 2, 17, 0, 0, 0, 3, 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