Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a20465e80c32099b8a7a14a1ed035c6c57dc4253020114dce6c001a0f127f524

Tx prefix hash: 11b957d5c6d6e8892c57bf412c5ba4d5a0d1d691eea8472f95d55428ea57f05e
Tx public key: 1550cb94d124f34e5e693ffab0baad52905d6c4414529082436b2bf92f52878e
Timestamp: 1707862051 Timestamp [UCT]: 2024-02-13 22:07:31 Age [y:d:h:m:s]: 01:059:22:53:55
Block: 956927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303893 RingCT/type: yes/0
Extra: 011550cb94d124f34e5e693ffab0baad52905d6c4414529082436b2bf92f52878e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69cf15651a00f2ecd1e4a21b323bbaf7274f06a3c0a9a65eab95c06237fd66c9 0.600000000000 1416239 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": 956937, "vin": [ { "gen": { "height": 956927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69cf15651a00f2ecd1e4a21b323bbaf7274f06a3c0a9a65eab95c06237fd66c9" } } ], "extra": [ 1, 21, 80, 203, 148, 209, 36, 243, 78, 94, 105, 63, 250, 176, 186, 173, 82, 144, 93, 108, 68, 20, 82, 144, 130, 67, 107, 43, 249, 47, 82, 135, 142, 2, 17, 0, 0, 0, 5, 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