← previous blocknext block →recent activity
Analyzing
Block #86,339,505
23 transactions · 19 stateful · 2026-07-08 04:51:15 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,339,505 · 23 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
2w03w14w05w16w012w116w117w218w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
6 touches
3 conflicts
0x034f1f86…4e8d
0x34b655…2a6f
4 touches
1 conflict
0x0586955b…2aaf
0x34b655…2a6f
4 touches
1 conflict
0x060aae4e…f1d0
0x34b655…2a6f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x1630ed91…9774
0x34b655…2a6f
4 touches
1 conflict
0x289f9358…7567
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity