← previous blocknext block →recent activity
Analyzing
Block #100,787,396
18 transactions · 16 stateful · 2026-08-31 15:06:30 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,787,396 · 18 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
4w06w07w18w29w010w113w115w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 conflicts
0x489d7033…e8e1
0x34b655…2a6f
2 touches
0 conflicts
0x4e58deff…c5d0
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity