Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a966cecf581793dbefbcf0cf7e170563e545809d2e6c48d152216e8489fe44f1

Tx prefix hash: 06c772b3fe08bf61d93fa33f5cdde5f7ad90362c0364e70d224c6335dbb623b6
Tx public key: 8bd277f327f8cacf9333e4b39bb0e24666b7da639c907d8235529631a929107f
Timestamp: 1705702700 Timestamp [UCT]: 2024-01-19 22:18:20 Age [y:d:h:m:s]: 01:262:09:19:14
Block: 938993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446308 RingCT/type: yes/0
Extra: 018bd277f327f8cacf9333e4b39bb0e24666b7da639c907d8235529631a929107f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df8aa55952616baf3a3e040a171259d1b6386236244aadc2f3836c7785b0f9c0 0.600000000000 1397077 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": 939003, "vin": [ { "gen": { "height": 938993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df8aa55952616baf3a3e040a171259d1b6386236244aadc2f3836c7785b0f9c0" } } ], "extra": [ 1, 139, 210, 119, 243, 39, 248, 202, 207, 147, 51, 228, 179, 155, 176, 226, 70, 102, 183, 218, 99, 156, 144, 125, 130, 53, 82, 150, 49, 169, 41, 16, 127, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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