Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7dffb2a0ebc6bd14522c51d5959f36052efd7397e91d1f5775e673d1515aba0

Tx prefix hash: f09001a1de34b65809ae67c7b042af4eca7042e9f4e6d78c97590bb3c92d4dae
Tx public key: c8400964fb9dfddce20ab38b1a3db62062c53042320b9e2cc03ab6b81bbfaa33
Timestamp: 1720692760 Timestamp [UCT]: 2024-07-11 10:12:40 Age [y:d:h:m:s]: 00:340:06:40:54
Block: 1063312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243061 RingCT/type: yes/0
Extra: 01c8400964fb9dfddce20ab38b1a3db62062c53042320b9e2cc03ab6b81bbfaa33021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3af44ca512d7f1c80a2386e4ff8c13dfe1d49d0e617be6454d6131ed9132a7da 0.600000000000 1533827 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": 1063322, "vin": [ { "gen": { "height": 1063312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3af44ca512d7f1c80a2386e4ff8c13dfe1d49d0e617be6454d6131ed9132a7da" } } ], "extra": [ 1, 200, 64, 9, 100, 251, 157, 253, 220, 226, 10, 179, 139, 26, 61, 182, 32, 98, 197, 48, 66, 50, 11, 158, 44, 192, 58, 182, 184, 27, 191, 170, 51, 2, 17, 0, 0, 0, 3, 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