Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47f8229618109ce954577a71333c033fb4da198c2bf61f367bf1830591b4c49f

Tx prefix hash: 9b0781f2baf951b24fc276446dff6f9f73b596680dc2bc65ab1640c88c27b9e3
Tx public key: 03763d9ec8403db96ef101b5372949a9034bc5c21c30b9acfd0d967489d4ca8a
Timestamp: 1720696240 Timestamp [UCT]: 2024-07-11 11:10:40 Age [y:d:h:m:s]: 00:227:08:39:12
Block: 1063334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162382 RingCT/type: yes/0
Extra: 0103763d9ec8403db96ef101b5372949a9034bc5c21c30b9acfd0d967489d4ca8a02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7484ab55f6df46f0e6e3cb71497d5e7b0cd078ef464dd97b7e4f02ced20e529e 0.600000000000 1533849 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": 1063344, "vin": [ { "gen": { "height": 1063334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7484ab55f6df46f0e6e3cb71497d5e7b0cd078ef464dd97b7e4f02ced20e529e" } } ], "extra": [ 1, 3, 118, 61, 158, 200, 64, 61, 185, 110, 241, 1, 181, 55, 41, 73, 169, 3, 75, 197, 194, 28, 48, 185, 172, 253, 13, 150, 116, 137, 212, 202, 138, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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