← previous blocknext block →recent activity
Analyzing
Block #100,607,270
22 transactions · 17 stateful · 2026-08-31 00:00:16 UTC
Parallelism
86/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,607,270 · 22 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
2w03w14w25w06w110w011w112w214w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xa0a8ac53…199c
0xa6afd3…d132
6 touches
3 conflicts
0x88ecacda…04c9
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb9a1532e…d4cc
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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: 0xf5b5f7f8…a36d70
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity