← previous blocknext block →recent activity
Analyzing
Block #100,584,542
28 transactions · 21 stateful · 2026-08-30 22:05:55 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,584,542 · 28 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
1w05w06w07w19w010w111w116w119w221w323w426w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7ad475a…0e41
0x34b655…2a6f
6 touches
3 conflicts
0x331c0ab9…8179
0x34b655…2a6f
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xe7ad475a4a…4e0e41
Audit this contract →
← previous block·next block →recent activity