Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5de43399a536cb97e0f81d65043c8cce972c904531d308fb5008946d494cfffe

Tx prefix hash: f8ba2f3c06eb043edc1e90cfdcea9f9a1c1d2b04c44f9dd24db46f15925b400a
Tx public key: a397d3092dee215f2cf43182a5270efb516b1d59f8b3c508fafab811eca1fa68
Timestamp: 1705943909 Timestamp [UCT]: 2024-01-22 17:18:29 Age [y:d:h:m:s]: 01:008:12:27:31
Block: 940987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267170 RingCT/type: yes/0
Extra: 01a397d3092dee215f2cf43182a5270efb516b1d59f8b3c508fafab811eca1fa6802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afbfad15a50d5a259597e86c8c1168e2227cb646c1e8d7bbbf82cc230a2b28f7 0.600000000000 1399129 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": 940997, "vin": [ { "gen": { "height": 940987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afbfad15a50d5a259597e86c8c1168e2227cb646c1e8d7bbbf82cc230a2b28f7" } } ], "extra": [ 1, 163, 151, 211, 9, 45, 238, 33, 95, 44, 244, 49, 130, 165, 39, 14, 251, 81, 107, 29, 89, 248, 179, 197, 8, 250, 250, 184, 17, 236, 161, 250, 104, 2, 17, 0, 0, 0, 1, 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