Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96820b0b3c382f788e5160fc357ec0c173516bb5d13ed9db34b2d18e1aad3823

Tx prefix hash: 1a0e295eec7e8dc4e2864325cfb8bf1fc52f66bb802cb088d7b232dee83cdcf2
Tx public key: 1bba9b153d37b0b77484ae8a868f565f1e5e695cea01f440361dcf673c6616e8
Timestamp: 1710532809 Timestamp [UCT]: 2024-03-15 20:00:09 Age [y:d:h:m:s]: 01:238:05:51:38
Block: 979086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428959 RingCT/type: yes/0
Extra: 011bba9b153d37b0b77484ae8a868f565f1e5e695cea01f440361dcf673c6616e80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 962c77860b7f01e91b2b7367b2372fff3af099fb6fcc3dd5ce01bcd38018aecf 0.600000000000 1439117 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": 979096, "vin": [ { "gen": { "height": 979086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "962c77860b7f01e91b2b7367b2372fff3af099fb6fcc3dd5ce01bcd38018aecf" } } ], "extra": [ 1, 27, 186, 155, 21, 61, 55, 176, 183, 116, 132, 174, 138, 134, 143, 86, 95, 30, 94, 105, 92, 234, 1, 244, 64, 54, 29, 207, 103, 60, 102, 22, 232, 2, 17, 0, 0, 0, 2, 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