Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81c3e43c6a73b5f0a7333e7cbbb9a9e9bada85783dea3ae0d78f4d4b81f89cca

Tx prefix hash: 33a3611110030468f1265faa8e50fea068f780d6e2d56c11f1ed0a7722da11ba
Tx public key: 7c638b9717f155c5c327d1eff191f4b4860d9a4a947831778b2939e70a327a84
Timestamp: 1703626289 Timestamp [UCT]: 2023-12-26 21:31:29 Age [y:d:h:m:s]: 01:024:11:51:17
Block: 921810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278810 RingCT/type: yes/0
Extra: 017c638b9717f155c5c327d1eff191f4b4860d9a4a947831778b2939e70a327a84021100000005ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d74addb784ef7795010798332e39dee77619f109bfe541c54f2d1aba7d0bb2b 0.600000000000 1379504 of 15

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": 921820, "vin": [ { "gen": { "height": 921810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d74addb784ef7795010798332e39dee77619f109bfe541c54f2d1aba7d0bb2b" } } ], "extra": [ 1, 124, 99, 139, 151, 23, 241, 85, 197, 195, 39, 209, 239, 241, 145, 244, 180, 134, 13, 154, 74, 148, 120, 49, 119, 139, 41, 57, 231, 10, 50, 122, 132, 2, 17, 0, 0, 0, 5, 173, 86, 148, 172, 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