Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ce94ad4dab30e103f3951e74c9de7320d49af043ac600bec7482396876ae2db

Tx prefix hash: 49610f33251ff73bb4771f5ca634f8e5ddaca72aef7827ae17cc5561df109080
Tx public key: a0bbcd5898df3d9b4a96fc2dea60672ebb2aaf1defd153d72d4013dc2677b90c
Timestamp: 1702606806 Timestamp [UCT]: 2023-12-15 02:20:06 Age [y:d:h:m:s]: 01:344:07:59:25
Block: 913349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504974 RingCT/type: yes/0
Extra: 01a0bbcd5898df3d9b4a96fc2dea60672ebb2aaf1defd153d72d4013dc2677b90c021100000006faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f9cbbfb2a34e1854862a1957398d8b6b8f59f252c18483b24224c8bd5c8d6c0 0.600000000000 1370617 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": 913359, "vin": [ { "gen": { "height": 913349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f9cbbfb2a34e1854862a1957398d8b6b8f59f252c18483b24224c8bd5c8d6c0" } } ], "extra": [ 1, 160, 187, 205, 88, 152, 223, 61, 155, 74, 150, 252, 45, 234, 96, 103, 46, 187, 42, 175, 29, 239, 209, 83, 215, 45, 64, 19, 220, 38, 119, 185, 12, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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