Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06cfe80d706f809f5f4e8571e02a64f2c4033251a947388af7e719d8847d2333

Tx prefix hash: bd76406ea9506e1629fede62b005c9f8ea0c1a0e189161458a4466bfbea0636b
Tx public key: d738e07e6cf0965a40f0d862ad2afd80f9514c108f54679b8623013981346d3e
Timestamp: 1706306896 Timestamp [UCT]: 2024-01-26 22:08:16 Age [y:d:h:m:s]: 01:029:13:29:23
Block: 944002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282190 RingCT/type: yes/0
Extra: 01d738e07e6cf0965a40f0d862ad2afd80f9514c108f54679b8623013981346d3e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32707f60e93a8c4ec0459b57c1db8dc209004aaae62f6638d84c9d9a94b22a29 0.600000000000 1402228 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": 944012, "vin": [ { "gen": { "height": 944002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32707f60e93a8c4ec0459b57c1db8dc209004aaae62f6638d84c9d9a94b22a29" } } ], "extra": [ 1, 215, 56, 224, 126, 108, 240, 150, 90, 64, 240, 216, 98, 173, 42, 253, 128, 249, 81, 76, 16, 143, 84, 103, 155, 134, 35, 1, 57, 129, 52, 109, 62, 2, 17, 0, 0, 0, 4, 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