Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab384d79d6c25cb556b090bc0ca5354688ca0e67178052205dccb05ffc5dadae

Tx prefix hash: 00410c0659bd59b919b167d1044208d456fdbb92d67e3ceae2029d985df73db0
Tx public key: e820d953bb3c6b1502fb0a4c14e1d67277135d19dd53d87e7eeb1a1d5f88f3e1
Timestamp: 1709498076 Timestamp [UCT]: 2024-03-03 20:34:36 Age [y:d:h:m:s]: 00:272:12:52:21
Block: 970498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195115 RingCT/type: yes/0
Extra: 01e820d953bb3c6b1502fb0a4c14e1d67277135d19dd53d87e7eeb1a1d5f88f3e10211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8f071466a8c770f1a0b4188796ef747e48d5be5a2f18eadaece29b52c26fa72 0.600000000000 1430355 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": 970508, "vin": [ { "gen": { "height": 970498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8f071466a8c770f1a0b4188796ef747e48d5be5a2f18eadaece29b52c26fa72" } } ], "extra": [ 1, 232, 32, 217, 83, 187, 60, 107, 21, 2, 251, 10, 76, 20, 225, 214, 114, 119, 19, 93, 25, 221, 83, 216, 126, 126, 235, 26, 29, 95, 136, 243, 225, 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