Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad9b07a36c75322885609558e8ab14e9119f553dd55039cdbed3066759d600f0

Tx prefix hash: 5dbaaa89b9d933270acf280af6f3b33a547d57ff7381dee5d84ad6cd9813c7b3
Tx public key: 91299b1438d449c8670e1e393a269f4b2b3a50ba0d57c7e614fd44e563ab7834
Timestamp: 1705402319 Timestamp [UCT]: 2024-01-16 10:51:59 Age [y:d:h:m:s]: 01:342:19:02:54
Block: 936514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503864 RingCT/type: yes/0
Extra: 0191299b1438d449c8670e1e393a269f4b2b3a50ba0d57c7e614fd44e563ab783402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a1e30ff37b7d2e8f1f38b8b25ab4695606ec6d7024ecbaac80855908be7e694 0.600000000000 1394542 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": 936524, "vin": [ { "gen": { "height": 936514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a1e30ff37b7d2e8f1f38b8b25ab4695606ec6d7024ecbaac80855908be7e694" } } ], "extra": [ 1, 145, 41, 155, 20, 56, 212, 73, 200, 103, 14, 30, 57, 58, 38, 159, 75, 43, 58, 80, 186, 13, 87, 199, 230, 20, 253, 68, 229, 99, 171, 120, 52, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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