← previous blocknext block →recent activity
Analyzing
Block #83,640,570
23 transactions · 19 stateful · 2026-06-25 16:56:58 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,640,570 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w111w012w113w214w315w416w517w621w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x1222e42d…7dc8
0x34b655…2a6f
8 touches
6 conflicts
0x2e86dd1e…dc3e
0x34b655…2a6f
6 touches
3 conflicts
0x0cdf9369…5331
0x34b655…2a6f
6 touches
3 conflicts
0x66c4b84f…f002
0x34b655…2a6f
4 touches
1 conflict
0x77eb0a91…f15e
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity