Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c08b80967d4f58604587533e7471867a9eed95ec8c75705c3514dd6f299e6b

Tx prefix hash: 005bc0e0b6424ff86f2fa2c353a5ef290b22aa4d1f2686b3ec44c5391bb59b12
Tx public key: a37059d10fab84a350146d1c5c1591037f6383dc6c23bdf9b67d046a511d014c
Timestamp: 1703127876 Timestamp [UCT]: 2023-12-21 03:04:36 Age [y:d:h:m:s]: 01:091:14:49:11
Block: 917697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326581 RingCT/type: yes/0
Extra: 01a37059d10fab84a350146d1c5c1591037f6383dc6c23bdf9b67d046a511d014c021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a3b7c1c5a0797848bf124dab6ed3db261857996e322af76b2505a2b9a6a535 0.600000000000 1375279 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": 917707, "vin": [ { "gen": { "height": 917697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a3b7c1c5a0797848bf124dab6ed3db261857996e322af76b2505a2b9a6a535" } } ], "extra": [ 1, 163, 112, 89, 209, 15, 171, 132, 163, 80, 20, 109, 28, 92, 21, 145, 3, 127, 99, 131, 220, 108, 35, 189, 249, 182, 125, 4, 106, 81, 29, 1, 76, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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