Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dba11bdc2bc4ff0a2b7e18fc0fedb298d378551719b50cfd79ab1fed2da4e77b

Tx prefix hash: d5f53e6e1853d49f5f2134aba40f2adfa354faa73569b2880cfe39b1a34670ae
Tx public key: b8d6ecfd6b1e16620409e82a9500fc4c6e2ec1516f4c6f4c0faf274814b3a7e8
Timestamp: 1717834222 Timestamp [UCT]: 2024-06-08 08:10:22 Age [y:d:h:m:s]: 01:156:11:20:11
Block: 1039608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370398 RingCT/type: yes/0
Extra: 01b8d6ecfd6b1e16620409e82a9500fc4c6e2ec1516f4c6f4c0faf274814b3a7e802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2d255b1c3b7995b5a91932017fe1ce61ded0cccdc8e8a4775f6fd0cc2c37dce 0.600000000000 1508251 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": 1039618, "vin": [ { "gen": { "height": 1039608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2d255b1c3b7995b5a91932017fe1ce61ded0cccdc8e8a4775f6fd0cc2c37dce" } } ], "extra": [ 1, 184, 214, 236, 253, 107, 30, 22, 98, 4, 9, 232, 42, 149, 0, 252, 76, 110, 46, 193, 81, 111, 76, 111, 76, 15, 175, 39, 72, 20, 179, 167, 232, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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