Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71da88eb641b561523e109065c5aa23767f97054b66a7ce37bedf062cc1096b7

Tx prefix hash: c64bb61d9e38d4ab542f5b8eadaed925b47157aaaca0d782d15c90f7879df233
Tx public key: 85ebc9681b654b9685da0a10656c96ecc1cfb7cdcfb1c40c32e65d50b8e82e19
Timestamp: 1725037634 Timestamp [UCT]: 2024-08-30 17:07:14 Age [y:d:h:m:s]: 00:176:12:04:15
Block: 1099314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125961 RingCT/type: yes/0
Extra: 0185ebc9681b654b9685da0a10656c96ecc1cfb7cdcfb1c40c32e65d50b8e82e1902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ec64fce02fb000ea6d27a1443f057e32abb0dbc2eb38a603f5f11853a84612 0.600000000000 1575273 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": 1099324, "vin": [ { "gen": { "height": 1099314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ec64fce02fb000ea6d27a1443f057e32abb0dbc2eb38a603f5f11853a84612" } } ], "extra": [ 1, 133, 235, 201, 104, 27, 101, 75, 150, 133, 218, 10, 16, 101, 108, 150, 236, 193, 207, 183, 205, 207, 177, 196, 12, 50, 230, 93, 80, 184, 232, 46, 25, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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