← previous blocknext block →recent activity
Analyzing
Block #84,572,595
23 transactions · 18 stateful · 2026-06-30 00:30:17 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,572,595 · 23 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
3w05w09w110w214w015w116w118w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0x8ba6a4bd…3d99
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x235dd62b…f416
0x34b655…2a6f
4 touches
1 conflict
0x2666137c…e4ea
0x34b655…2a6f
4 touches
1 conflict
0x2965e2d6…5800
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x38c58d5f…1d25
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
3 conflicts on slot 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity