Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f41bac340b6cb8428ccaddf8c7a72a06d250cae8f0ab474da76637fd310b35

Tx prefix hash: e7997290bbbe69a137c8377754eccab12ded64d032d591331e77f033fd708a5a
Tx public key: e694270ae58c72378c00c06dedfb675c40c1e4bd4f79c7ae239d05dbfb542bb9
Timestamp: 1579230306 Timestamp [UCT]: 2020-01-17 03:05:06 Age [y:d:h:m:s]: 05:021:06:53:39
Block: 47176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165387 RingCT/type: yes/0
Extra: 01e694270ae58c72378c00c06dedfb675c40c1e4bd4f79c7ae239d05dbfb542bb9021100000001ff58ae94000000000000000000

1 output(s) for total of 428.239935961000 dcy

stealth address amount amount idx
00: eb608d835afe4d682b6b7b2f68cfaac7a96d116eaf63512e8bed560efcf91ad3 428.239935961000 87179 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": 47186, "vin": [ { "gen": { "height": 47176 } } ], "vout": [ { "amount": 428239935961, "target": { "key": "eb608d835afe4d682b6b7b2f68cfaac7a96d116eaf63512e8bed560efcf91ad3" } } ], "extra": [ 1, 230, 148, 39, 10, 229, 140, 114, 55, 140, 0, 192, 109, 237, 251, 103, 92, 64, 193, 228, 189, 79, 121, 199, 174, 35, 157, 5, 219, 251, 84, 43, 185, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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