Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c9b2ee1a48acab91117d65ab7bb004c4ee4a6c83b9b8ac598b633be6e3e66b

Tx prefix hash: 8814fd30871d12653a5333ee609cf22df7273273f40ae4e0ca733d7823ff40df
Tx public key: afe0d3e332eda7e4954796e6e8d3c5070eabf7db5220895154f55b9b356a40ea
Timestamp: 1725924331 Timestamp [UCT]: 2024-09-09 23:25:31 Age [y:d:h:m:s]: 00:186:16:28:57
Block: 1106671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133269 RingCT/type: yes/0
Extra: 01afe0d3e332eda7e4954796e6e8d3c5070eabf7db5220895154f55b9b356a40ea02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a57589e63c79158806e7043d8b333a563b3459bfee895f3e3d0efcf48636aacd 0.600000000000 1584272 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": 1106681, "vin": [ { "gen": { "height": 1106671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a57589e63c79158806e7043d8b333a563b3459bfee895f3e3d0efcf48636aacd" } } ], "extra": [ 1, 175, 224, 211, 227, 50, 237, 167, 228, 149, 71, 150, 230, 232, 211, 197, 7, 14, 171, 247, 219, 82, 32, 137, 81, 84, 245, 91, 155, 53, 106, 64, 234, 2, 17, 0, 0, 0, 10, 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