← previous blocknext block →recent activity
Analyzing
Block #83,640,845
11 transactions · 9 stateful · 2026-06-25 16:58:48 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,640,845 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ae827f1…aa36
0x34b655…2a6f
6 touches
3 conflicts
0xdf20d62c…e281
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda5e0705…ecb9
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x366ded2c…0d9e
0x34b655…2a6f
2 touches
0 conflicts
0x7e6c970a…65af
0x34b655…2a6f
2 touches
0 conflicts
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
3 conflicts on slot 0x8ae827f129…5daa36
Audit this contract →
← previous block·next block →recent activity