Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862daec0efe2b09007cea5f0a432534efb0f918e0454d984cec715d8c2d26427

Tx prefix hash: ebc5771c5a4c89328f03d2092fb14df41bf44e5c23da5c56ead3ce04180398f7
Tx public key: c53dd60bacd8eadd833c2e180135e1247c331fafe744bbe157b08da8a72e4b6f
Timestamp: 1703806332 Timestamp [UCT]: 2023-12-28 23:32:12 Age [y:d:h:m:s]: 01:359:03:53:31
Block: 923296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515588 RingCT/type: yes/0
Extra: 01c53dd60bacd8eadd833c2e180135e1247c331fafe744bbe157b08da8a72e4b6f0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87fa79efde3b53044943eef032bda3fb78b6d7e1c5e1966c93a0b6afc8841fb3 0.600000000000 1381024 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": 923306, "vin": [ { "gen": { "height": 923296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87fa79efde3b53044943eef032bda3fb78b6d7e1c5e1966c93a0b6afc8841fb3" } } ], "extra": [ 1, 197, 61, 214, 11, 172, 216, 234, 221, 131, 60, 46, 24, 1, 53, 225, 36, 124, 51, 31, 175, 231, 68, 187, 225, 87, 176, 141, 168, 167, 46, 75, 111, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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