← previous blocknext block →recent activity
Analyzing
Block #86,248,164
24 transactions · 18 stateful · 2026-07-07 18:41:22 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,248,164 · 24 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
1w03w04w15w16w07w113w214w021w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe8b6e4c2…e20a
0x188d58…ea8e
4 touches
1 conflict
0xe8b6e4c2…e20b
0x188d58…ea8e
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0dbf9688…c6cf
0x43cf54…7777
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x4c9744df…d092
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 0x3bdd71a21a…eeb6eb
Audit this contract →
← previous block·next block →recent activity