Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0483ac97a10ed1852c9b6d9d0c5df04ffc8664cf819c8a9269b4f2e5bce1a6a1

Tx prefix hash: ca8e42492b11869d44ecf06b334868bb1007dd81341b7033f37b777948fec9d0
Tx public key: 664e15ee8ac67255b8d57d24ad8438b58d7b2e7166090615b5f384c68b1738ba
Timestamp: 1714750239 Timestamp [UCT]: 2024-05-03 15:30:39 Age [y:d:h:m:s]: 00:269:03:50:51
Block: 1014037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192394 RingCT/type: yes/0
Extra: 01664e15ee8ac67255b8d57d24ad8438b58d7b2e7166090615b5f384c68b1738ba0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbbeb4d21b2a239e6df811a5de52900df3e1cffca3ebd68096f81121cb49cc27 0.600000000000 1477016 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": 1014047, "vin": [ { "gen": { "height": 1014037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbbeb4d21b2a239e6df811a5de52900df3e1cffca3ebd68096f81121cb49cc27" } } ], "extra": [ 1, 102, 78, 21, 238, 138, 198, 114, 85, 184, 213, 125, 36, 173, 132, 56, 181, 141, 123, 46, 113, 102, 9, 6, 21, 181, 243, 132, 198, 139, 23, 56, 186, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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