Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a88419ffa66672fd76559e3d4fc705ed6a0349de751e2e0523b1af235a5b93b

Tx prefix hash: 35b3f5095c204437948846c49cfe8adb7df7dee63dd99e6dae3512950b0ecc70
Tx public key: 158aa81d04a977c0d388de5b9b1c97ddc317eebc878f89e847fd2cfb1c103473
Timestamp: 1708771983 Timestamp [UCT]: 2024-02-24 10:53:03 Age [y:d:h:m:s]: 01:052:09:33:14
Block: 964475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298470 RingCT/type: yes/0
Extra: 01158aa81d04a977c0d388de5b9b1c97ddc317eebc878f89e847fd2cfb1c10347302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad2fa37de8e4ad410f5aa3eb89317a445cda9b90cc6d28375598c87102953de5 0.600000000000 1424216 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": 964485, "vin": [ { "gen": { "height": 964475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad2fa37de8e4ad410f5aa3eb89317a445cda9b90cc6d28375598c87102953de5" } } ], "extra": [ 1, 21, 138, 168, 29, 4, 169, 119, 192, 211, 136, 222, 91, 155, 28, 151, 221, 195, 23, 238, 188, 135, 143, 137, 232, 71, 253, 44, 251, 28, 16, 52, 115, 2, 17, 0, 0, 0, 1, 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