← previous blocknext block →recent activity
Analyzing
Block #86,225,398
30 transactions · 23 stateful · 2026-07-07 16:09:16 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,225,398 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w312w014w115w216w317w422w423w524w625w726w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x44ad89ba…cf83
0x0a917f…7777
10 touches
10 conflicts
0x1ccfa324…0b93
0x0a917f…7777
10 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
10 touches
10 conflicts
0xe6f2ae57…2026
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x431fed…d150
10 touches
10 conflicts
0x00000000…0002
0x431fed…d150
10 touches
10 conflicts
0x00000000…0003
0x431fed…d150
10 touches
10 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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity