← previous blocknext block →recent activity
Analyzing
Block #100,705,326
21 transactions · 21 stateful · 2026-08-31 08:13:30 UTC
Parallelism
81/100
Blocked
24%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,705,326 · 21 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
4w06w08w111w112w213w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
8 touches
6 conflicts
0x329f9fde…fe9c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd97b0449…00a0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xf28ea1d1…1fb8
0x34b655…2a6f
4 touches
1 conflict
0x1456f7c9…ca2d
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 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity