← previous blocknext block →recent activity
Analyzing
Block #99,937,854
23 transactions · 22 stateful · 2026-08-28 15:47:17 UTC
Parallelism
78/100
Blocked
45%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,937,854 · 23 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
1w03w04w15w26w07w18w29w310w211w314w116w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd6538fb…2b3f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3a41314b…a9c8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x07f51f85…f593
0x34b655…2a6f
4 touches
1 conflict
0x32530ce0…0a5f
0x34b655…2a6f
4 touches
1 conflict
0x4387ba94…e195
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 0xdd6538fbaf…632b3f
Audit this contract →
← previous block·next block →recent activity