Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5001f7b36908a1f5b04d3f4ffb546493afc990a9948d7817247b35c2fc8198e8

Tx prefix hash: 5a0895b91b25ff30942857888031ce256729b4a553c5d65a34a377edcfab2b3f
Tx public key: 34f623eb8f53726fff419040ab39b327a02c83741e9bdcdbd13a0f8a2b37add1
Timestamp: 1700970063 Timestamp [UCT]: 2023-11-26 03:41:03 Age [y:d:h:m:s]: 01:095:19:20:52
Block: 899786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329606 RingCT/type: yes/0
Extra: 0134f623eb8f53726fff419040ab39b327a02c83741e9bdcdbd13a0f8a2b37add102110000000675e3f0e9000000000000000000

1 output(s) for total of 0.640671562000 dcy

stealth address amount amount idx
00: e644965a30cf9f6e5dfd27350f4aa640cf61530ad3e280f9145e922eb31ccda0 0.640671562000 1356249 of 0

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": 899796, "vin": [ { "gen": { "height": 899786 } } ], "vout": [ { "amount": 640671562, "target": { "key": "e644965a30cf9f6e5dfd27350f4aa640cf61530ad3e280f9145e922eb31ccda0" } } ], "extra": [ 1, 52, 246, 35, 235, 143, 83, 114, 111, 255, 65, 144, 64, 171, 57, 179, 39, 160, 44, 131, 116, 30, 155, 220, 219, 209, 58, 15, 138, 43, 55, 173, 209, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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