Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3fb07937804d1e763c08d5b6ba072dc080b99c5c549ee4521854013902bbc8

Tx prefix hash: 068376208550df1e3f6bda95a3141b98477ba029a850efc2741f33976f44546e
Tx public key: 01c61a2353f097119799f60fbbffb0d8ecc73b4c7cf9052c18ae1b9e8190dd9f
Timestamp: 1712015004 Timestamp [UCT]: 2024-04-01 23:43:24 Age [y:d:h:m:s]: 01:058:16:48:16
Block: 991317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302998 RingCT/type: yes/0
Extra: 0101c61a2353f097119799f60fbbffb0d8ecc73b4c7cf9052c18ae1b9e8190dd9f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65ee4634945acf25c4f15055726e3a8a7f464b6306b5241838afd23c54ce9d3b 0.600000000000 1451651 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": 991327, "vin": [ { "gen": { "height": 991317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65ee4634945acf25c4f15055726e3a8a7f464b6306b5241838afd23c54ce9d3b" } } ], "extra": [ 1, 1, 198, 26, 35, 83, 240, 151, 17, 151, 153, 246, 15, 187, 255, 176, 216, 236, 199, 59, 76, 124, 249, 5, 44, 24, 174, 27, 158, 129, 144, 221, 159, 2, 17, 0, 0, 0, 7, 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