← previous blocknext block →recent activity
Analyzing
Block #86,988,412
28 transactions · 24 stateful · 2026-07-11 05:10:11 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,988,412 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w014w015w116w218w119w020w121w222w323w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a05ade0…672d
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x3347cbe5…846c
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x4caf91f9…8ab5
0x34b655…2a6f
6 touches
3 conflicts
0x5238dcb7…e0e2
0x34b655…2a6f
6 touches
3 conflicts
0x68d518d8…3932
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x1a05ade06f…bc672d
Audit this contract →
← previous block·next block →recent activity