← previous blocknext block →recent activity
Analyzing
Block #99,848,725
19 transactions · 15 stateful · 2026-08-28 08:18:02 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,848,725 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w413w514w616w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c67d31e…3dbe
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xabb9dd5a…5b5f
0x34b655…2a6f
6 touches
3 conflicts
0xcbfcbfd4…9251
0x34b655…2a6f
5 touches
3 conflicts
0x2d6af7d3…5e30
0x34b655…2a6f
4 touches
2 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
21 conflicts on slot 0x3c67d31e03…f03dbe
Audit this contract →
← previous block·next block →recent activity