← previous blocknext block →recent activity
Analyzing
Block #100,982,873
22 transactions · 22 stateful · 2026-09-01 07:30:03 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,982,873 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w28w310w317w020w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40afcb37…764e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc0c143b1…108b
0x34b655…2a6f
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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
3 conflicts on slot 0x40afcb378f…37764e
Audit this contract →
← previous block·next block →recent activity