Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0b96100ccccc420bd80739e881ba072a3ab0f5127b6c8db77e6f2e33627a48

Tx prefix hash: c1710c9af6110e185149aa813abca1f89d8f1391a28875debe541f6b46f408e3
Tx public key: be014b9ba544897d975aef09a82e5fdb1f954476978f58693209d9b4dabb1e87
Timestamp: 1711526802 Timestamp [UCT]: 2024-03-27 08:06:42 Age [y:d:h:m:s]: 01:013:00:18:31
Block: 987337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270243 RingCT/type: yes/0
Extra: 01be014b9ba544897d975aef09a82e5fdb1f954476978f58693209d9b4dabb1e870211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90548b0d81a10f1c89e1b5ed1fcbc67cd25e0c97ef0a70e61e890722fde6133f 0.600000000000 1447578 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": 987347, "vin": [ { "gen": { "height": 987337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90548b0d81a10f1c89e1b5ed1fcbc67cd25e0c97ef0a70e61e890722fde6133f" } } ], "extra": [ 1, 190, 1, 75, 155, 165, 68, 137, 125, 151, 90, 239, 9, 168, 46, 95, 219, 31, 149, 68, 118, 151, 143, 88, 105, 50, 9, 217, 180, 218, 187, 30, 135, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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