Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2168fbab2134d6e6ec21ac4e68dcf6d7114bb664a859de3ea8e69553f5d7ff0e

Tx prefix hash: 07e6b75e34d4f321eb2211affc2a54427716de086c2bbcd2946a8dbebd58b506
Tx public key: 7ea366d72c2ffdb3eddb930115df7dd48d206cd5cecfac8402f6d217a947444e
Timestamp: 1719783552 Timestamp [UCT]: 2024-06-30 21:39:12 Age [y:d:h:m:s]: 00:292:10:40:54
Block: 1055751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208982 RingCT/type: yes/0
Extra: 017ea366d72c2ffdb3eddb930115df7dd48d206cd5cecfac8402f6d217a947444e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc1175c79d6e496415b62861e7cb3b5fc4b2dbd425fd89b4b90edbcf4996caac 0.600000000000 1526156 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": 1055761, "vin": [ { "gen": { "height": 1055751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1175c79d6e496415b62861e7cb3b5fc4b2dbd425fd89b4b90edbcf4996caac" } } ], "extra": [ 1, 126, 163, 102, 215, 44, 47, 253, 179, 237, 219, 147, 1, 21, 223, 125, 212, 141, 32, 108, 213, 206, 207, 172, 132, 2, 246, 210, 23, 169, 71, 68, 78, 2, 17, 0, 0, 0, 3, 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