← previous blocknext block →recent activity
Analyzing
Block #100,705,157
30 transactions · 28 stateful · 2026-08-31 08:12:39 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,705,157 · 30 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
1w02w04w05w16w18w29w310w111w112w114w215w218w319w429w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27b6010e…e4aa
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xdc9915b5…542c
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x6ceb0938…d5b7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x89edbe7a…2479
0x34b655…2a6f
6 touches
3 conflicts
0x3914d795…63fd
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 0x27b6010e94…34e4aa
Audit this contract →
← previous block·next block →recent activity