← previous blocknext block →recent activity
Analyzing
Block #86,795,777
24 transactions · 16 stateful · 2026-07-10 07:42:26 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,795,777 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w013w014w115w116w117w118w222w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x98cc6884…3a83
0x34b655…2a6f
6 touches
3 conflicts
0xf0ad9713…5796
0x34b655…2a6f
6 touches
3 conflicts
0x1c03f81f…b303
0x34b655…2a6f
6 touches
3 conflicts
0x1c03f81f…b304
0x34b655…2a6f
6 touches
3 conflicts
0x5f743211…1321
0x34b655…2a6f
4 touches
1 conflict
0x9adb2803…81f1
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity