Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 467568e6d54929fff5c305e717802991e48bedc6380549a62050f58c36171524

Tx prefix hash: 770de1716f147db1d2858df04a9f12d5d3e28fefdf07cd0ab6bf3314fcea034e
Tx public key: e5aaed503b69221ea52366b6a34ac453cbf9f91dc0acc13929d9a781d0db3a42
Timestamp: 1704734903 Timestamp [UCT]: 2024-01-08 17:28:23 Age [y:d:h:m:s]: 01:048:04:02:02
Block: 930987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295499 RingCT/type: yes/0
Extra: 01e5aaed503b69221ea52366b6a34ac453cbf9f91dc0acc13929d9a781d0db3a4202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 675c079d3a5ed93fafd2be76644555cf44ed504c1b1639fd4be18d6f51e98a7e 0.600000000000 1388879 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": 930997, "vin": [ { "gen": { "height": 930987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "675c079d3a5ed93fafd2be76644555cf44ed504c1b1639fd4be18d6f51e98a7e" } } ], "extra": [ 1, 229, 170, 237, 80, 59, 105, 34, 30, 165, 35, 102, 182, 163, 74, 196, 83, 203, 249, 249, 29, 192, 172, 193, 57, 41, 217, 167, 129, 208, 219, 58, 66, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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