Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa192f8bfd67ed026d8e613eb70d91689735bdf759b6e154c1b0098fc21aa622

Tx prefix hash: 144e62278adc893427a49d3ff89d724a653f928bc9b08dea3a134650e73a284c
Tx public key: e74a1a9b3c6ae02a294f51e2281eec6271de2f704ea72a8462475f4ad2dce9d8
Timestamp: 1727908885 Timestamp [UCT]: 2024-10-02 22:41:25 Age [y:d:h:m:s]: 00:161:12:32:56
Block: 1123128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115242 RingCT/type: yes/0
Extra: 01e74a1a9b3c6ae02a294f51e2281eec6271de2f704ea72a8462475f4ad2dce9d8021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd34c44b8d34ec20ff94aec7ccf15a451cdd32017b7d50ba345f98184f1a8e81 0.600000000000 1605661 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": 1123138, "vin": [ { "gen": { "height": 1123128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd34c44b8d34ec20ff94aec7ccf15a451cdd32017b7d50ba345f98184f1a8e81" } } ], "extra": [ 1, 231, 74, 26, 155, 60, 106, 224, 42, 41, 79, 81, 226, 40, 30, 236, 98, 113, 222, 47, 112, 78, 167, 42, 132, 98, 71, 95, 74, 210, 220, 233, 216, 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