← previous blocknext block →recent activity
Analyzing
Block #100,732,289
26 transactions · 19 stateful · 2026-08-31 10:29:09 UTC
Parallelism
88/100
Blocked
26%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,732,289 · 26 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
3w06w012w015w019w120w121w122w023w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3d7c1f1…1f50
0x34b655…2a6f
4 touches
1 conflict
0xb26ff3de…9352
0xa6afd3…d132
4 touches
1 conflict
0x42daad7f…630b
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb81
0x1b6862…e19c
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
1 conflict on slot 0xe3d7c1f111…601f50
Audit this contract →
← previous block·next block →recent activity