← previous blocknext block →recent activity
Analyzing
Block #86,831,345
22 transactions · 19 stateful · 2026-07-10 11:40:22 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.55
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,831,345 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w310w415w516w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0xdfc58aa8…e1df
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00873542…6db6
0x34b655…2a6f
6 touches
3 conflicts
0x36510b9c…90d2
0x34b655…2a6f
4 touches
1 conflict
0x505d32fe…14ad
0x34b655…2a6f
4 touches
1 conflict
0x55c358f0…a0d0
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity