← previous blocknext block →recent activity
Analyzing
Block #86,733,414
18 transactions · 10 stateful · 2026-07-10 00:45:56 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,733,414 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x0d43cc69…6f83
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe46df8d3…e453
0x34b655…2a6f
4 touches
1 conflict
0x28262bcf…87b0
0x34b655…2a6f
4 touches
1 conflict
0x28262bcf…87b1
0x34b655…2a6f
4 touches
1 conflict
0xa04ccfce…e6ef
0x34b655…2a6f
4 touches
1 conflict
0x4293a398…286f
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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity