← previous blocknext block →recent activity
Analyzing
Block #100,791,267
18 transactions · 13 stateful · 2026-08-31 15:26:00 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,791,267 · 18 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
1w02w13w24w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54c6fb44…369a
0x34b655…2a6f
10 touches
10 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0x2bdb02ba…df95
0x34b655…2a6f
4 touches
1 conflict
0x75311cd9…b360
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9ec1d00b…52e6
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
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
10 conflicts on slot 0x54c6fb4487…3b369a
Audit this contract →
← previous block·next block →recent activity