Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aadd6586d490924603a5b6cea44e4567427907491503fbf936f1df1efd653c3f

Tx prefix hash: 4700062de3fe67577597e458be2dc8290fcb1b39c5f7de028dc426f641cbb072
Tx public key: dfae45c8cbbac426eab2d6152f8e59de5fb9e4b3864c89f8868b0690d81d56ff
Timestamp: 1724741328 Timestamp [UCT]: 2024-08-27 06:48:48 Age [y:d:h:m:s]: 00:243:17:10:44
Block: 1096854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174074 RingCT/type: yes/0
Extra: 01dfae45c8cbbac426eab2d6152f8e59de5fb9e4b3864c89f8868b0690d81d56ff021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22d1f56890989d914ddd86d1cce6d48f3e3d84349852f86e14230d8dc85d765f 0.600000000000 1572055 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": 1096864, "vin": [ { "gen": { "height": 1096854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22d1f56890989d914ddd86d1cce6d48f3e3d84349852f86e14230d8dc85d765f" } } ], "extra": [ 1, 223, 174, 69, 200, 203, 186, 196, 38, 234, 178, 214, 21, 47, 142, 89, 222, 95, 185, 228, 179, 134, 76, 137, 248, 134, 139, 6, 144, 216, 29, 86, 255, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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