← previous blocknext block →recent activity
Analyzing
Block #99,975,449
29 transactions · 23 stateful · 2026-08-28 18:56:43 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,975,449 · 29 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
1w02w14w05w07w19w010w011w120w221w323w225w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e6a8155…9636
0x34b655…2a6f
8 touches
6 conflicts
0xb8baf30a…1e1b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1e737223…2278
0x34b655…2a6f
6 touches
3 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x827bfdaf…88d0
0x34b655…2a6f
4 touches
1 conflict
0x94f5fc74…a10d
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
6 conflicts on slot 0x6e6a81554a…499636
Audit this contract →
← previous block·next block →recent activity