← previous blocknext block →recent activity
Analyzing
Block #100,982,554
24 transactions · 22 stateful · 2026-09-01 07:28:27 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,982,554 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
14 touches
21 conflicts
0xad80ed3d…c92a
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x88298878…f1fe
0x34b655…2a6f
6 touches
3 conflicts
0x66774a98…88c8
0x34b655…2a6f
4 touches
1 conflict
0x93e4c736…3731
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
21 conflicts on slot 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity