← previous blocknext block →recent activity
Analyzing
Block #86,222,146
27 transactions · 19 stateful · 2026-07-07 15:47:32 UTC
Parallelism
78/100
Blocked
37%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,222,146 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w012w113w014w115w221w222w323w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0000
0x431fed…d150
6 touches
3 conflicts
0xe6f2ae57…2026
0x3bd359…433a
6 touches
3 conflicts
0x1ccfa324…0b93
0x0a917f…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x0a917f…7777
6 touches
3 conflicts
0x00000000…0003
0x431fed…d150
6 touches
3 conflicts
0x00000000…0002
0x431fed…d150
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
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