← previous blocknext block →recent activity
Analyzing
Block #99,478,524
18 transactions · 16 stateful · 2026-08-27 01:01:34 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,478,524 · 18 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
1w02w13w26w07w110w011w312w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd814f518…f5b4
0x34b655…2a6f
8 touches
6 conflicts
0xf7640726…19a2
0x2a68ba…90c5
6 touches
3 conflicts
0x08d53462…97ef
0x2b46c0…1669
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x99b29f97…d502
0x851145…3f07
6 touches
3 conflicts
0xd9438fc3…f9a2
0x851145…3f07
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 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 0xd814f51828…c6f5b4
Audit this contract →
← previous block·next block →recent activity