Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e01289b9db0a4c82a89ae5f9ad9467bd17e18a9c702225be581e563bdd0871c

Tx prefix hash: 705d148af94fd78af4ae19b081c011b48279d1723462bd4fdb0aef999954212b
Tx public key: be00ac4354f2530f60aa1d9fa8c34e99b1bc8b13247d31eb560103b6d360da23
Timestamp: 1732421278 Timestamp [UCT]: 2024-11-24 04:07:58 Age [y:d:h:m:s]: 00:127:15:26:30
Block: 1160437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91038 RingCT/type: yes/0
Extra: 01be00ac4354f2530f60aa1d9fa8c34e99b1bc8b13247d31eb560103b6d360da230211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2febc2f1e66834d488c96a7ed11f4ad7d2e78fa8c24ea1ec05574a69288f3a0f 0.600000000000 1646084 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": 1160447, "vin": [ { "gen": { "height": 1160437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2febc2f1e66834d488c96a7ed11f4ad7d2e78fa8c24ea1ec05574a69288f3a0f" } } ], "extra": [ 1, 190, 0, 172, 67, 84, 242, 83, 15, 96, 170, 29, 159, 168, 195, 78, 153, 177, 188, 139, 19, 36, 125, 49, 235, 86, 1, 3, 182, 211, 96, 218, 35, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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