Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca6b95bb04ff9337527367b6d2046a944dfbe46f6c78299a3acbddfd706e6f9a

Tx prefix hash: ebad1979db5d5515fd2f080b4445e8553714d1cf97bf1d2a22a76d0f2e694410
Tx public key: d83b21cc4d0b578acf75dffe461ffeb5edd2cdfff42e254c423d87a6c144624b
Timestamp: 1725209727 Timestamp [UCT]: 2024-09-01 16:55:27 Age [y:d:h:m:s]: 00:173:01:14:44
Block: 1100747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123479 RingCT/type: yes/0
Extra: 01d83b21cc4d0b578acf75dffe461ffeb5edd2cdfff42e254c423d87a6c144624b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da01de9de6a43e9f4f8f2cb0f2458a5d809f6291fe7fea8897304965ef17b06d 0.600000000000 1576728 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": 1100757, "vin": [ { "gen": { "height": 1100747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da01de9de6a43e9f4f8f2cb0f2458a5d809f6291fe7fea8897304965ef17b06d" } } ], "extra": [ 1, 216, 59, 33, 204, 77, 11, 87, 138, 207, 117, 223, 254, 70, 31, 254, 181, 237, 210, 205, 255, 244, 46, 37, 76, 66, 61, 135, 166, 193, 68, 98, 75, 2, 17, 0, 0, 0, 3, 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