← previous blocknext block →recent activity
Analyzing
Block #100,984,368
33 transactions · 28 stateful · 2026-09-01 07:37:34 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,984,368 · 33 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
3w06w17w08w29w110w214w016w017w118w221w322w223w024w330w131w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54c6fb44…369a
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x624b573b…e8fc
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
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 0x54c6fb4487…3b369a
Audit this contract →
← previous block·next block →recent activity