← previous blocknext block →recent activity
Analyzing
Block #99,854,244
17 transactions · 16 stateful · 2026-08-28 08:45:49 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,854,244 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w49w510w512w115w016w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a8a0baf…767d
0x34b655…2a6f
10 touches
10 conflicts
0xc852b267…9d14
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49ec1ec1…ad02
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x6598fda9…7eb7
0x34b655…2a6f
4 touches
1 conflict
0x6719a767…9d62
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x2a8a0baf5d…0b767d
Audit this contract →
← previous block·next block →recent activity