Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d55d55d94fe30cf0053ce7b787992304496eafe2051f4519b56a326bdbea42e

Tx prefix hash: c0374f8ee74662238b96c42dc479a37ab4ac826a94953a6a2af639e1707f0bda
Tx public key: b47aa87eb5cbedc0de410dfc3bb2e88311b8f3dcfd86f8cb9eb89f2ab91637aa
Timestamp: 1694721724 Timestamp [UCT]: 2023-09-14 20:02:04 Age [y:d:h:m:s]: 01:208:15:04:30
Block: 848173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410203 RingCT/type: yes/0
Extra: 01b47aa87eb5cbedc0de410dfc3bb2e88311b8f3dcfd86f8cb9eb89f2ab91637aa021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.949840792000 dcy

stealth address amount amount idx
00: 273651a7d665aa9ce3d3852c2cfe5dd9b8fc9b4eaad3ad0ecf0ba7d140e78be3 0.949840792000 1301759 of 0

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": 848183, "vin": [ { "gen": { "height": 848173 } } ], "vout": [ { "amount": 949840792, "target": { "key": "273651a7d665aa9ce3d3852c2cfe5dd9b8fc9b4eaad3ad0ecf0ba7d140e78be3" } } ], "extra": [ 1, 180, 122, 168, 126, 181, 203, 237, 192, 222, 65, 13, 252, 59, 178, 232, 131, 17, 184, 243, 220, 253, 134, 248, 203, 158, 184, 159, 42, 185, 22, 55, 170, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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