Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cae54708e4c4b74baa2881711e86a10217fe1c8517025f79f3c8491610577ea3

Tx prefix hash: 827b3f0e11699ec7af6a0b5b2a4ea91a330234ae77d5436b4cfe4ac8c1bf9c23
Tx public key: 3346e86f678c38eda790f99ad6bba589c6db507b2f3f470bf3928487dd4e34a8
Timestamp: 1723308083 Timestamp [UCT]: 2024-08-10 16:41:23 Age [y:d:h:m:s]: 00:221:05:34:38
Block: 1084982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158015 RingCT/type: yes/0
Extra: 013346e86f678c38eda790f99ad6bba589c6db507b2f3f470bf3928487dd4e34a802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a2894c2e7e88c5db3dc0a3965dcc7d76aea75b7dfce7672eeae3793043aa739 0.600000000000 1559451 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": 1084992, "vin": [ { "gen": { "height": 1084982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a2894c2e7e88c5db3dc0a3965dcc7d76aea75b7dfce7672eeae3793043aa739" } } ], "extra": [ 1, 51, 70, 232, 111, 103, 140, 56, 237, 167, 144, 249, 154, 214, 187, 165, 137, 198, 219, 80, 123, 47, 63, 71, 11, 243, 146, 132, 135, 221, 78, 52, 168, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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