← previous blocknext block →recent activity
Analyzing
Block #86,681,342
14 transactions · 12 stateful · 2026-07-09 18:58:17 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,681,342 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06a48e8…d6d1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2d2ecca1…2d77
0x34b655…2a6f
2 touches
0 conflicts
0x31519d10…f76b
0x34b655…2a6f
2 touches
0 conflicts
0x5bb46f6c…7693
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
1 conflict on slot 0xb06a48e8ed…47d6d1
Audit this contract →
← previous block·next block →recent activity