← previous blocknext block →recent activity
Analyzing
Block #86,752,624
13 transactions · 10 stateful · 2026-07-10 02:54:23 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,752,624 · 13 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
2w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa84e1c73…0c49
0x34b655…2a6f
4 touches
1 conflict
0xea31bd73…9e9c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2a010631…6941
0x34b655…2a6f
2 touches
0 conflicts
0x410b84ab…1dbc
0x34b655…2a6f
2 touches
0 conflicts
0x430b92ea…6f54
0x34b655…2a6f
2 touches
0 conflicts
0x52d6e6b4…7ff5
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 0xa84e1c7314…0f0c49
Audit this contract →
← previous block·next block →recent activity