Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1591f91288848cf0af1d956283c605bf7e5fe1c1f5bac6137eb257b5564a64fe

Tx prefix hash: d6fa88556b2fa48d37e1a11ab08a95814701bb9d0463e2aa56191cfa65d1eba3
Tx public key: 8b9effa30f36cbe26f99bc9f935e62aa6393d9414e7de6b2b15809fe5c820759
Timestamp: 1711968244 Timestamp [UCT]: 2024-04-01 10:44:04 Age [y:d:h:m:s]: 01:057:15:45:30
Block: 990931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302249 RingCT/type: yes/0
Extra: 018b9effa30f36cbe26f99bc9f935e62aa6393d9414e7de6b2b15809fe5c8207590211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c54b66994a038531fca1f7cacda568ade0f34ee0dc38ac588bbe59553329fef7 0.600000000000 1451263 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": 990941, "vin": [ { "gen": { "height": 990931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c54b66994a038531fca1f7cacda568ade0f34ee0dc38ac588bbe59553329fef7" } } ], "extra": [ 1, 139, 158, 255, 163, 15, 54, 203, 226, 111, 153, 188, 159, 147, 94, 98, 170, 99, 147, 217, 65, 78, 125, 230, 178, 177, 88, 9, 254, 92, 130, 7, 89, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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