Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a39074c31b34b43afc83c4cbc82c5f4cb3f8c3aff85fb079258ac047d4a927c

Tx prefix hash: f8b8e1513f6bca557bd5be1a4d1c8485a7a275533a502f6a65434f35d499aaf1
Tx public key: c9af8e2814fc0cb2f000d8a9b45f61e56d907aba6269b8381732931f7f1a44be
Timestamp: 1712188700 Timestamp [UCT]: 2024-04-03 23:58:20 Age [y:d:h:m:s]: 01:032:18:45:36
Block: 992769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284432 RingCT/type: yes/0
Extra: 01c9af8e2814fc0cb2f000d8a9b45f61e56d907aba6269b8381732931f7f1a44be0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a91903bf2d22fc35fb8f6932271691b0f0d40382b462f66aac53e6beddbf2b0a 0.600000000000 1453143 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": 992779, "vin": [ { "gen": { "height": 992769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a91903bf2d22fc35fb8f6932271691b0f0d40382b462f66aac53e6beddbf2b0a" } } ], "extra": [ 1, 201, 175, 142, 40, 20, 252, 12, 178, 240, 0, 216, 169, 180, 95, 97, 229, 109, 144, 122, 186, 98, 105, 184, 56, 23, 50, 147, 31, 127, 26, 68, 190, 2, 17, 0, 0, 0, 3, 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