Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9dbb6ac997dc45ddc358f9a2c5e0381549cec4f1622eaf61918fd8babee93a

Tx prefix hash: 8975f3121b9606eb1a8c6865b1057fe97dfe7edc34e8101d90c0615cdbeaea91
Tx public key: 36e179a2eda086f3ef24e969e2073991b6b96eced5b9bb79c812123a097ac999
Timestamp: 1699402742 Timestamp [UCT]: 2023-11-08 00:19:02 Age [y:d:h:m:s]: 01:017:04:35:38
Block: 886792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273665 RingCT/type: yes/0
Extra: 0136e179a2eda086f3ef24e969e2073991b6b96eced5b9bb79c812123a097ac99902110000000275e3f0e9000000000000000000

1 output(s) for total of 0.707440602000 dcy

stealth address amount amount idx
00: 46cbd093fd2c471b32056cda25ba6602acb45763242b8e427067c658d209e2b8 0.707440602000 1342635 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": 886802, "vin": [ { "gen": { "height": 886792 } } ], "vout": [ { "amount": 707440602, "target": { "key": "46cbd093fd2c471b32056cda25ba6602acb45763242b8e427067c658d209e2b8" } } ], "extra": [ 1, 54, 225, 121, 162, 237, 160, 134, 243, 239, 36, 233, 105, 226, 7, 57, 145, 182, 185, 110, 206, 213, 185, 187, 121, 200, 18, 18, 58, 9, 122, 201, 153, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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