← previous blocknext block →recent activity
Analyzing
Block #100,584,432
21 transactions · 18 stateful · 2026-08-30 22:05:22 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,584,432 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w19w010w111w014w115w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacccd944…736a
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0x764c3e36…c6db
0x34b655…2a6f
4 touches
1 conflict
0x7e0948eb…ba58
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x8a9538e6…08df
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
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 0xacccd9440c…a2736a
Audit this contract →
← previous block·next block →recent activity