← previous blocknext block →recent activity
Analyzing
Block #100,631,086
11 transactions · 11 stateful · 2026-08-31 02:00:04 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,631,086 · 11 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
4w05w06w17w010w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a95f394…be66
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x36918c55…8424
0x34b655…2a6f
4 touches
1 conflict
0x7a12283f…b18a
0x34ae4d…3fc5
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 0x5a95f394d8…29be66
Audit this contract →
← previous block·next block →recent activity