Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a5967b8a779831984f548dfd2ffc309a64a00afa62ebfc6b79180f237ea7c2

Tx prefix hash: de96d5e6d569514190c25ee32f304154b5bbf5a4bf5291253626390f8ce21d5f
Tx public key: 610efaea059031e675c896635c0c1d9b04f1adc8db19d1ef0a5a8688a7433e8b
Timestamp: 1581083180 Timestamp [UCT]: 2020-02-07 13:46:20 Age [y:d:h:m:s]: 04:282:14:40:57
Block: 60197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093803 RingCT/type: yes/0
Extra: 01610efaea059031e675c896635c0c1d9b04f1adc8db19d1ef0a5a8688a7433e8b021100000003724f989b000000000000000000

1 output(s) for total of 387.742287471000 dcy

stealth address amount amount idx
00: f1b53b96308c2f66cdc4499b695fc033890205f84397b1e0f80b5c229c7c3f94 387.742287471000 111045 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": 60207, "vin": [ { "gen": { "height": 60197 } } ], "vout": [ { "amount": 387742287471, "target": { "key": "f1b53b96308c2f66cdc4499b695fc033890205f84397b1e0f80b5c229c7c3f94" } } ], "extra": [ 1, 97, 14, 250, 234, 5, 144, 49, 230, 117, 200, 150, 99, 92, 12, 29, 155, 4, 241, 173, 200, 219, 25, 209, 239, 10, 90, 134, 136, 167, 67, 62, 139, 2, 17, 0, 0, 0, 3, 114, 79, 152, 155, 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