← previous blocknext block →recent activity
Analyzing
Block #100,454,284
12 transactions · 11 stateful · 2026-08-30 11:10:39 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,454,284 · 12 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
2w04w17w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd59c545a…f179
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2802fd4f…6c0c
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
2 touches
0 conflicts
0x36dae541…eef2
0x34b655…2a6f
2 touches
0 conflicts
0x5e7e0120…7bb9
0x34b655…2a6f
2 touches
0 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xd59c545a6c…0bf179
Audit this contract →
← previous block·next block →recent activity