← previous blocknext block →recent activity
Analyzing
Block #86,225,286
30 transactions · 23 stateful · 2026-07-07 16:08:31 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,225,286 · 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
1w02w13w04w15w213w317w018w119w220w325w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ccfa324…0b93
0x0a917f…7777
8 touches
6 conflicts
0x44ad89ba…cf83
0x0a917f…7777
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xe6f2ae57…2026
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x431fed…d150
8 touches
6 conflicts
0x00000000…0002
0x431fed…d150
8 touches
6 conflicts
0x00000000…0003
0x431fed…d150
8 touches
6 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: 0x0a917fcc…9d7777
6 conflicts on slot 0x1ccfa32498…500b93
Audit this contract →
← previous block·next block →recent activity