Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bd08d401fe9a57751ace3130ffc91236f6677454b8960f0d29d7b8a2abe9f51

Tx prefix hash: 78a4752149012dd99fa10d5c0e82175f98ea6c92203460521b0c4737a32a518a
Tx public key: a8b131b7a9fabb3456c34216ceaf574717d816833fc3a755aa947d8a8292e859
Timestamp: 1705996862 Timestamp [UCT]: 2024-01-23 08:01:02 Age [y:d:h:m:s]: 01:077:22:07:18
Block: 941431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316795 RingCT/type: yes/0
Extra: 01a8b131b7a9fabb3456c34216ceaf574717d816833fc3a755aa947d8a8292e85902110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ebd07526ce6a69fb9f7eb3b8a1653a3c40ed59bf1d7882ab0a7485ccc3ecfb6 0.600000000000 1399577 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": 941441, "vin": [ { "gen": { "height": 941431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ebd07526ce6a69fb9f7eb3b8a1653a3c40ed59bf1d7882ab0a7485ccc3ecfb6" } } ], "extra": [ 1, 168, 177, 49, 183, 169, 250, 187, 52, 86, 195, 66, 22, 206, 175, 87, 71, 23, 216, 22, 131, 63, 195, 167, 85, 170, 148, 125, 138, 130, 146, 232, 89, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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