← previous blocknext block →recent activity
Analyzing
Block #100,730,188
21 transactions · 21 stateful · 2026-08-31 10:18:35 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,730,188 · 21 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
4w07w19w210w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
8 touches
6 conflicts
0x0a523508…d9b0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x1894f5b2…cb94
0x34b655…2a6f
2 touches
0 conflicts
0x1f7afd69…7774
0x34b655…2a6f
2 touches
0 conflicts
0x25180879…8191
0x34b655…2a6f
2 touches
0 conflicts
0x2827ae77…4368
0x34b655…2a6f
2 touches
0 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 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity