Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834ad971ba0caf7e3b7ce131ba25d48d910de1fe6f6d0ebd305b93094e95da52

Tx prefix hash: 62639b679dbbab36e6a37749e0a1628234b19d4fc670876cca52e5e6e4590798
Tx public key: 35bfcffec9d14a0c6a2c5a4a85dc491c3778628215f65b4d398c7fa92682e10c
Timestamp: 1729547616 Timestamp [UCT]: 2024-10-21 21:53:36 Age [y:d:h:m:s]: 00:001:01:21:51
Block: 1136668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768 RingCT/type: yes/0
Extra: 0135bfcffec9d14a0c6a2c5a4a85dc491c3778628215f65b4d398c7fa92682e10c0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb077fecc2079d0a842b24ee268dec3c31a0a1b5c373f0aaeef3d71aef24d05 0.600000000000 1620015 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": 1136678, "vin": [ { "gen": { "height": 1136668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb077fecc2079d0a842b24ee268dec3c31a0a1b5c373f0aaeef3d71aef24d05" } } ], "extra": [ 1, 53, 191, 207, 254, 201, 209, 74, 12, 106, 44, 90, 74, 133, 220, 73, 28, 55, 120, 98, 130, 21, 246, 91, 77, 57, 140, 127, 169, 38, 130, 225, 12, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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