← previous blocknext block →recent activity
Analyzing
Block #86,245,643
24 transactions · 18 stateful · 2026-07-07 18:24:30 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,245,643 · 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
4w05w111w012w113w216w017w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1e9a8e72…7138
0x43cf54…7777
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x207cc41e…57c6
0x34b655…2a6f
4 touches
1 conflict
0x9c79b492…a68c
0x34b655…2a6f
2 touches
0 conflicts
0xae085366…fa10
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6425
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity