Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d68a201b39d8316054a3237f2889aac4fa03ba6e710533049e3e6e39b744aebf

Tx prefix hash: 5c9d0cfb2c4aad12b858d7fd1ce6f054f9141b4938afe21812edd1c86ea339c3
Tx public key: c699564bbf004228cc4d70b32211c4f849eb3ed7093f56011d2689248b2a9cc6
Timestamp: 1729232265 Timestamp [UCT]: 2024-10-18 06:17:45 Age [y:d:h:m:s]: 00:146:10:53:23
Block: 1134097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104447 RingCT/type: yes/0
Extra: 01c699564bbf004228cc4d70b32211c4f849eb3ed7093f56011d2689248b2a9cc6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e3f21bd4f7f11f8386bbb6e772afd81f1b815b3f6ef77991ff1dcfd3b851aeb 0.600000000000 1617346 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": 1134107, "vin": [ { "gen": { "height": 1134097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e3f21bd4f7f11f8386bbb6e772afd81f1b815b3f6ef77991ff1dcfd3b851aeb" } } ], "extra": [ 1, 198, 153, 86, 75, 191, 0, 66, 40, 204, 77, 112, 179, 34, 17, 196, 248, 73, 235, 62, 215, 9, 63, 86, 1, 29, 38, 137, 36, 139, 42, 156, 198, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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