← previous blocknext block →recent activity
Analyzing
Block #86,836,931
22 transactions · 18 stateful · 2026-07-10 12:17:43 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,836,931 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w06w19w110w211w319w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1dab3b8…1ab6
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc8c54a2d…0f66
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x16363afe…d410
0x34b655…2a6f
4 touches
1 conflict
0x2db904c4…3199
0x34b655…2a6f
4 touches
1 conflict
0x4e9832a1…7b8c
0x34b655…2a6f
4 touches
1 conflict
0x533a1b36…3e30
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 0xf1dab3b8b2…3b1ab6
Audit this contract →
← previous block·next block →recent activity