← previous blocknext block →recent activity
Analyzing
Block #86,829,160
19 transactions · 17 stateful · 2026-07-10 11:25:46 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,829,160 · 19 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
1w02w16w08w19w210w013w314w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9b9caa88…69f3
0x34b655…2a6f
6 touches
3 conflicts
0x41d7e149…baec
0x34b655…2a6f
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x20103d86…5e90
0x34b655…2a6f
4 touches
1 conflict
0x8b501dcf…1040
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity