Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52684637fb2e2f95e6c62587d24803c3ed3c73d67b4d2abe1245bdb845640368

Tx prefix hash: 729f1d1fb8f972872899a527e85ff7e7932c8911afd98a39eda1f8526fa51622
Tx public key: 51f3e3d28ad6cf7456c918dc8b6960b11aff065c8fc5f2edb3520dde5f8caced
Timestamp: 1708873889 Timestamp [UCT]: 2024-02-25 15:11:29 Age [y:d:h:m:s]: 01:256:12:23:57
Block: 965322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442060 RingCT/type: yes/0
Extra: 0151f3e3d28ad6cf7456c918dc8b6960b11aff065c8fc5f2edb3520dde5f8caced02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a94da90d8514cd4c004fb430d9b2d9fbd1816fed07a5ce4cf146e4953cec7447 0.600000000000 1425071 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": 965332, "vin": [ { "gen": { "height": 965322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a94da90d8514cd4c004fb430d9b2d9fbd1816fed07a5ce4cf146e4953cec7447" } } ], "extra": [ 1, 81, 243, 227, 210, 138, 214, 207, 116, 86, 201, 24, 220, 139, 105, 96, 177, 26, 255, 6, 92, 143, 197, 242, 237, 179, 82, 13, 222, 95, 140, 172, 237, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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