Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2dce8ae1bb06a5761f043b4acb091b9c570748fa0084b3caa3dd696bd9ce08e

Tx prefix hash: d32e35da096c5fd1c4fbc153c044f81b49d8b5a0f92778d3b00a0f19f2fc8fde
Tx public key: 8c370b1e54c5aff15ddbb44668dc687d91b7de7fd251698ea6cc84d277561710
Timestamp: 1733105977 Timestamp [UCT]: 2024-12-02 02:19:37 Age [y:d:h:m:s]: 00:110:09:23:01
Block: 1166113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78697 RingCT/type: yes/0
Extra: 018c370b1e54c5aff15ddbb44668dc687d91b7de7fd251698ea6cc84d277561710021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cf8e484467dea97766042158ff5916da3d2d1d5d5f6f737af6ecac0605d1e44 0.600000000000 1651790 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": 1166123, "vin": [ { "gen": { "height": 1166113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cf8e484467dea97766042158ff5916da3d2d1d5d5f6f737af6ecac0605d1e44" } } ], "extra": [ 1, 140, 55, 11, 30, 84, 197, 175, 241, 93, 219, 180, 70, 104, 220, 104, 125, 145, 183, 222, 127, 210, 81, 105, 142, 166, 204, 132, 210, 119, 86, 23, 16, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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