← previous blocknext block →recent activity
Analyzing
Block #99,993,069
26 transactions · 25 stateful · 2026-08-28 20:25:29 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,993,069 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w112w014w115w216w317w118w221w424w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f45ff61…51da
0x34b655…2a6f
10 touches
10 conflicts
0x9d9f3717…44e7
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xef9d4724…ec5f
0x34b655…2a6f
6 touches
3 conflicts
0xd2d7cba8…9c3a
0x34b655…2a6f
6 touches
3 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x8f45ff617d…8651da
Audit this contract →
← previous block·next block →recent activity