Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 697d0e46ceb8f48f90714b9e56681cd3177b3f3030a5a7e52c9abec91977bb06

Tx prefix hash: cd3b7880fff9bfdee5e1c1ef01c0672adf2071740aec83c96bdc07fe97fb2ca5
Tx public key: e5449ea5d0dc6afb942359e36b40a7b26f5e891a8a85dc959672c6ade58d0e43
Timestamp: 1679642946 Timestamp [UCT]: 2023-03-24 07:29:06 Age [y:d:h:m:s]: 01:295:01:53:17
Block: 723880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471766 RingCT/type: yes/0
Extra: 01e5449ea5d0dc6afb942359e36b40a7b26f5e891a8a85dc959672c6ade58d0e43021100000004e7ace25d000000000000000000

1 output(s) for total of 2.451799439000 dcy

stealth address amount amount idx
00: c023009977518ea6dc9bd5c07d360a1062e781b11c4f4676a121769549620091 2.451799439000 1168873 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": 723890, "vin": [ { "gen": { "height": 723880 } } ], "vout": [ { "amount": 2451799439, "target": { "key": "c023009977518ea6dc9bd5c07d360a1062e781b11c4f4676a121769549620091" } } ], "extra": [ 1, 229, 68, 158, 165, 208, 220, 106, 251, 148, 35, 89, 227, 107, 64, 167, 178, 111, 94, 137, 26, 138, 133, 220, 149, 150, 114, 198, 173, 229, 141, 14, 67, 2, 17, 0, 0, 0, 4, 231, 172, 226, 93, 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