Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f187af2e413c7697303bed06f24c9bc7418dc81128a5670be92d402d8d0c3e

Tx prefix hash: c54e02c006506d6f91246915140d6fb088f2d2a51e9ab2e77951b5c4547366ef
Tx public key: ac368ff5c0cd7c85d69c458bfc681ee433aa1037a6077d3a31c6169f65153b27
Timestamp: 1726544669 Timestamp [UCT]: 2024-09-17 03:44:29 Age [y:d:h:m:s]: 00:068:10:17:17
Block: 1111813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48922 RingCT/type: yes/0
Extra: 01ac368ff5c0cd7c85d69c458bfc681ee433aa1037a6077d3a31c6169f65153b27021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88f541889e50fcfae582b5bbd7b846623eb64e06b87a31449e04cdda94b02d8 0.600000000000 1590902 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": 1111823, "vin": [ { "gen": { "height": 1111813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88f541889e50fcfae582b5bbd7b846623eb64e06b87a31449e04cdda94b02d8" } } ], "extra": [ 1, 172, 54, 143, 245, 192, 205, 124, 133, 214, 156, 69, 139, 252, 104, 30, 228, 51, 170, 16, 55, 166, 7, 125, 58, 49, 198, 22, 159, 101, 21, 59, 39, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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