← previous blocknext block →recent activity
Analyzing
Block #86,257,570
19 transactions · 17 stateful · 2026-07-07 19:44:14 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,257,570 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w110w011w112w213w314w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xafd8d502…d359
0x34b655…2a6f
8 touches
6 conflicts
0x08d66073…e706
0x34b655…2a6f
6 touches
3 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
6 touches
3 conflicts
0xe9452241…95a3
0x34b655…2a6f
6 touches
3 conflicts
0x02060180…fe50
0x34b655…2a6f
6 touches
3 conflicts
0xb6abb885…ce9c
0x34b655…2a6f
6 touches
3 conflicts
0xbb4fd99a…afa6
0x34b655…2a6f
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity