← previous blocknext block →recent activity
Analyzing
Block #83,672,144
16 transactions · 15 stateful · 2026-06-25 20:27:33 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,672,144 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w110w111w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f4c5cb2…cbee
0x34b655…2a6f
8 touches
6 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x574daf66…1c15
0x34b655…2a6f
4 touches
1 conflict
0x63860705…3e2e
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x7c77a512…0882
0x34b655…2a6f
4 touches
1 conflict
0x9ec861cc…36c8
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
6 conflicts on slot 0x8f4c5cb24a…f7cbee
Audit this contract →
← previous block·next block →recent activity