Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6e4c685f6d9253175eba4c6ff210f172b0cab7eb94c8597ddd0294df12a90e

Tx prefix hash: f93740cbf6e09e4890b45bbcf6aed022a1c1634e37c549699f4c7f318dbcf4d2
Tx public key: e7ab921a6837ad32209ce322b6fe74ff66b9f4cc96af0d11a8f294b9c272ada5
Timestamp: 1719221054 Timestamp [UCT]: 2024-06-24 09:24:14 Age [y:d:h:m:s]: 00:325:13:30:30
Block: 1051090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232668 RingCT/type: yes/0
Extra: 01e7ab921a6837ad32209ce322b6fe74ff66b9f4cc96af0d11a8f294b9c272ada50211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.619380000000 dcy

stealth address amount amount idx
00: 9fe60cb2a320200e1a78e72128764387f061b9aa7b98d468949092a80f72c7ca 0.619380000000 1521315 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": 1051100, "vin": [ { "gen": { "height": 1051090 } } ], "vout": [ { "amount": 619380000, "target": { "key": "9fe60cb2a320200e1a78e72128764387f061b9aa7b98d468949092a80f72c7ca" } } ], "extra": [ 1, 231, 171, 146, 26, 104, 55, 173, 50, 32, 156, 227, 34, 182, 254, 116, 255, 102, 185, 244, 204, 150, 175, 13, 17, 168, 242, 148, 185, 194, 114, 173, 165, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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