Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e5e069fdb7a3b49920094786e8951fa0a9b1c1e33357ccaef36a7070dbe3b1

Tx prefix hash: a4b795257f69e77e3b285e6ad696b83f4d783462e34fa40d3d7e9b3f92b9691c
Tx public key: 7e8d8f4f19cc25f5355982376e7685369e11ec692c23ee2459958cd63fd54ff6
Timestamp: 1720540522 Timestamp [UCT]: 2024-07-09 15:55:22 Age [y:d:h:m:s]: 00:141:23:55:03
Block: 1062043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101614 RingCT/type: yes/0
Extra: 017e8d8f4f19cc25f5355982376e7685369e11ec692c23ee2459958cd63fd54ff6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37ee0fefd9441992ea98c5d9c7d31946357d155156d4f0284f5b568b0166a576 0.600000000000 1532544 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": 1062053, "vin": [ { "gen": { "height": 1062043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37ee0fefd9441992ea98c5d9c7d31946357d155156d4f0284f5b568b0166a576" } } ], "extra": [ 1, 126, 141, 143, 79, 25, 204, 37, 245, 53, 89, 130, 55, 110, 118, 133, 54, 158, 17, 236, 105, 44, 35, 238, 36, 89, 149, 140, 214, 63, 213, 79, 246, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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