Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e294d5892faaffa48f3c64ef70688b5885fdf2323267c4d03d5d8830ca2c7fbb

Tx prefix hash: 9a558d7fc4e812e7aa69e5c7411293d15910145fc108bc3d5e08349db07bf050
Tx public key: 9d8e1d04d6f86ed5563b4b4020bafb055e5010d7f636cffde3c0339615fd10c1
Timestamp: 1731920632 Timestamp [UCT]: 2024-11-18 09:03:52 Age [y:d:h:m:s]: 00:136:10:37:25
Block: 1156288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97326 RingCT/type: yes/0
Extra: 019d8e1d04d6f86ed5563b4b4020bafb055e5010d7f636cffde3c0339615fd10c1021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 170b76fc21c671a564d238d8b37c85b63538aec29eda74cd92fd4d69b9d8c84a 0.600000000000 1641911 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": 1156298, "vin": [ { "gen": { "height": 1156288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "170b76fc21c671a564d238d8b37c85b63538aec29eda74cd92fd4d69b9d8c84a" } } ], "extra": [ 1, 157, 142, 29, 4, 214, 248, 110, 213, 86, 59, 75, 64, 32, 186, 251, 5, 94, 80, 16, 215, 246, 54, 207, 253, 227, 192, 51, 150, 21, 253, 16, 193, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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