← previous blocknext block →recent activity
Analyzing
Block #100,433,111
17 transactions · 16 stateful · 2026-08-30 09:24:02 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
1.06
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,433,111 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w28w110w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x005321e0…2e05
0x34b655…2a6f
8 touches
6 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
8 touches
6 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x4db508b8…b746
0x34b655…2a6f
4 touches
1 conflict
0x4f850ac3…1670
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 0x005321e088…9c2e05
Audit this contract →
← previous block·next block →recent activity