Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b081077134c6ad8d02760e643df00e1cc3a624c2edceec52d1e75794253c199

Tx prefix hash: f53e1dd295a916f5c519da83966412730faf6e1a0d6fe5385c727e94325b6d81
Tx public key: ba453670cf94e84e7a4bd713a05a019f5747c6ba4e66dd8334267beae4ed9cc9
Timestamp: 1711785209 Timestamp [UCT]: 2024-03-30 07:53:29 Age [y:d:h:m:s]: 01:047:18:42:02
Block: 989474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295113 RingCT/type: yes/0
Extra: 01ba453670cf94e84e7a4bd713a05a019f5747c6ba4e66dd8334267beae4ed9cc902110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e243ecd562532edcbc49bba1525a5a7f4c1403c34be839a0c741fbdff43db099 0.600000000000 1449771 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": 989484, "vin": [ { "gen": { "height": 989474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e243ecd562532edcbc49bba1525a5a7f4c1403c34be839a0c741fbdff43db099" } } ], "extra": [ 1, 186, 69, 54, 112, 207, 148, 232, 78, 122, 75, 215, 19, 160, 90, 1, 159, 87, 71, 198, 186, 78, 102, 221, 131, 52, 38, 123, 234, 228, 237, 156, 201, 2, 17, 0, 0, 0, 5, 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