← previous blocknext block →recent activity
Analyzing
Block #100,266,886
24 transactions · 19 stateful · 2026-08-29 19:25:24 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,266,886 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w08w19w211w016w317w418w519w220w622w423w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x162eae5d…7dd7
0x34b655…2a6f
10 touches
10 conflicts
0xfe45073e…6315
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x152ab4b2…7fee
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0x831f75b4…945d
0x34b655…2a6f
6 touches
3 conflicts
0x607e2ee6…7595
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
10 conflicts on slot 0x162eae5dcb…727dd7
Audit this contract →
← previous block·next block →recent activity