← previous blocknext block →recent activity
Analyzing
Block #86,511,504
14 transactions · 12 stateful · 2026-07-09 00:00:26 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,511,504 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2cd98078…527c
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x3411bf66…d778
0xd32edf…ff58
3 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x591a782e…e9ed
0x065c9d…c394
2 touches
0 conflicts
0x878d1cb5…9038
0x065c9d…c394
2 touches
0 conflicts
0x991a8cc8…39e1
0x065c9d…c394
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity