Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03777234d5a0efedf27f104e837b9d91fd6ce3d6c6246c1e7b14dce5c236be7

Tx prefix hash: b1264673bb8bcaad318da00751b3c539510178a5b4a8d9291710079c974219c5
Tx public key: b9f6092b8f80625ff8f0ac4383ebb1e0c1910c8d0fd2f08d70edf5c2581af088
Timestamp: 1735113115 Timestamp [UCT]: 2024-12-25 07:51:55 Age [y:d:h:m:s]: 00:093:14:26:46
Block: 1182751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66660 RingCT/type: yes/0
Extra: 01b9f6092b8f80625ff8f0ac4383ebb1e0c1910c8d0fd2f08d70edf5c2581af0880211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d21e0aec57a3f2d378117a52a88c1e00df36f58be6cd96ea9a4264eb0f26de4f 0.600000000000 1669188 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": 1182761, "vin": [ { "gen": { "height": 1182751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d21e0aec57a3f2d378117a52a88c1e00df36f58be6cd96ea9a4264eb0f26de4f" } } ], "extra": [ 1, 185, 246, 9, 43, 143, 128, 98, 95, 248, 240, 172, 67, 131, 235, 177, 224, 193, 145, 12, 141, 15, 210, 240, 141, 112, 237, 245, 194, 88, 26, 240, 136, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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