Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299aae40deda19d8e3eba68d687aa66cc4a3d618cea56e0174e8fc2d2a89bfbf

Tx prefix hash: 30b074b803962d9a37206a798ef91be72cc4b365804b452ffc46317295546bde
Tx public key: b4209fd343ca09f78afad56b9b90cd751a2d2e5c893f9f60ba9e0772d11923cf
Timestamp: 1720166039 Timestamp [UCT]: 2024-07-05 07:53:59 Age [y:d:h:m:s]: 00:347:04:22:10
Block: 1058927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248023 RingCT/type: yes/0
Extra: 01b4209fd343ca09f78afad56b9b90cd751a2d2e5c893f9f60ba9e0772d11923cf02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beec18f1c3ad3d070aebda5b258c43420d38b2e0cf441f65a8d56a718150e438 0.600000000000 1529386 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": 1058937, "vin": [ { "gen": { "height": 1058927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beec18f1c3ad3d070aebda5b258c43420d38b2e0cf441f65a8d56a718150e438" } } ], "extra": [ 1, 180, 32, 159, 211, 67, 202, 9, 247, 138, 250, 213, 107, 155, 144, 205, 117, 26, 45, 46, 92, 137, 63, 159, 96, 186, 158, 7, 114, 209, 25, 35, 207, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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