Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c8d4a3a2b229d92b604fe83ac71b8ea69e704926ef6bcb1ae8a921dfc831b99

Tx prefix hash: b72c82c2e38b30c88e689ad0feed8a88c175adc3f7a30e27193531127ecbd279
Tx public key: c933d4bd4cc697ab70a391cc96db55935c75e80dfa93a7bcab926aead5572cf8
Timestamp: 1574738392 Timestamp [UCT]: 2019-11-26 03:19:52 Age [y:d:h:m:s]: 05:341:19:47:59
Block: 17617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1384629 RingCT/type: yes/0
Extra: 01c933d4bd4cc697ab70a391cc96db55935c75e80dfa93a7bcab926aead5572cf8021100000001f95225a5000000000000000000

1 output(s) for total of 536.572543707000 dcy

stealth address amount amount idx
00: f03bd096747fdc0cbf8d57252d32f245a4e6ba35d55ecde22de2e97e420c3bab 536.572543707000 25873 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": 17627, "vin": [ { "gen": { "height": 17617 } } ], "vout": [ { "amount": 536572543707, "target": { "key": "f03bd096747fdc0cbf8d57252d32f245a4e6ba35d55ecde22de2e97e420c3bab" } } ], "extra": [ 1, 201, 51, 212, 189, 76, 198, 151, 171, 112, 163, 145, 204, 150, 219, 85, 147, 92, 117, 232, 13, 250, 147, 167, 188, 171, 146, 106, 234, 213, 87, 44, 248, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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