Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 975d1304b2318558fef3aa49a5a330393910f5f82ceeff10fe6044c167c82bed

Tx prefix hash: 8e5acfc595bf6e666f186db79c80948f4d8803efa5c514d46620fe0e637d9f4d
Tx public key: ce36f4e159b54b8c7b19bbeb60ee5833b4ce1fb4c69b0b1a0b5c83da36e4b715
Timestamp: 1700435750 Timestamp [UCT]: 2023-11-19 23:15:50 Age [y:d:h:m:s]: 01:100:14:52:34
Block: 895356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333055 RingCT/type: yes/0
Extra: 01ce36f4e159b54b8c7b19bbeb60ee5833b4ce1fb4c69b0b1a0b5c83da36e4b715021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.662695287000 dcy

stealth address amount amount idx
00: 2ee27f46429dc3473f85e5e80a620058341f8695de82e9e3e4e0c1d00c4688a1 0.662695287000 1351587 of 0

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": 895366, "vin": [ { "gen": { "height": 895356 } } ], "vout": [ { "amount": 662695287, "target": { "key": "2ee27f46429dc3473f85e5e80a620058341f8695de82e9e3e4e0c1d00c4688a1" } } ], "extra": [ 1, 206, 54, 244, 225, 89, 181, 75, 140, 123, 25, 187, 235, 96, 238, 88, 51, 180, 206, 31, 180, 198, 155, 11, 26, 11, 92, 131, 218, 54, 228, 183, 21, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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