← previous blocknext block →recent activity
Analyzing
Block #86,820,333
14 transactions · 12 stateful · 2026-07-10 10:26:35 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,820,333 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1feae76…0834
0x34b655…2a6f
8 touches
6 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
6 touches
3 conflicts
0x78f9dd3b…66e1
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74b737c4…05f3
0x34b655…2a6f
4 touches
1 conflict
0x78346476…4311
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 0xe1feae76e9…ec0834
Audit this contract →
← previous block·next block →recent activity