← previous blocknext block →recent activity
Analyzing
Block #86,057,095
30 transactions · 26 stateful · 2026-07-06 21:25:55 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,057,095 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w19w010w111w016w117w218w119w120w325w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xed5ebe25…d541
0xd32edf…ff58
7 touches
6 conflicts
0x18aed20c…48f3
0x000000…012a
6 touches
3 conflicts
0x335a161d…fe7f
0x000000…012a
6 touches
3 conflicts
0x7c403af1…31b1
0x3bd359…433a
6 touches
3 conflicts
0x591dbad0…662d
0x699abc…6a3b
6 touches
3 conflicts
0x8e1d4b50…f09f
0x699abc…6a3b
6 touches
3 conflicts
0x00000000…0000
0xd5b70d…615b
6 touches
3 conflicts
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