← previous blocknext block →recent activity
Analyzing
Block #99,860,756
11 transactions · 11 stateful · 2026-08-28 09:18:49 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,860,756 · 11 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
1w03w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cf31547…051b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0eb8a571…2efe
0x34b655…2a6f
4 touches
1 conflict
0x0d7c2b9a…66e1
0x34b655…2a6f
2 touches
0 conflicts
0x13d3acc8…b9fb
0x34b655…2a6f
2 touches
0 conflicts
0x25eb7079…cb76
0x34b655…2a6f
2 touches
0 conflicts
0x266d3847…7c89
0x34b655…2a6f
2 touches
0 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
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
6 conflicts on slot 0x3cf315478f…41051b
Audit this contract →
← previous block·next block →recent activity