← previous blocknext block →recent activity
Analyzing
Block #100,613,176
10 transactions · 9 stateful · 2026-08-31 00:29:58 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,613,176 · 10 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
3w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a39a2a4…857b
0x34b655…2a6f
6 touches
3 conflicts
0x814ba1ee…5451
0x34b655…2a6f
6 touches
3 conflicts
0xf72228f6…970c
0x34b655…2a6f
4 touches
1 conflict
0xf778799e…2698
0x34b655…2a6f
4 touches
1 conflict
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x5b05cce4…77be
0x34b655…2a6f
2 touches
0 conflicts
0x8e116aa5…8acc
0x34b655…2a6f
2 touches
0 conflicts
0xccebf5c5…8758
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
3 conflicts on slot 0x4a39a2a411…a6857b
Audit this contract →
← previous block·next block →recent activity