← previous blocknext block →recent activity
Analyzing
Block #86,364,243
26 transactions · 14 stateful · 2026-07-08 07:36:16 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,364,243 · 26 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
1w03w06w112w214w322w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xe770c81e…80cb
0xd32edf…ff58
5 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa958d271…bccd
0x065c9d…c394
4 touches
1 conflict
0x410d5ec0…6664
0x065c9d…c394
3 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
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