← previous blocknext block →recent activity
Analyzing
Block #100,617,291
25 transactions · 24 stateful · 2026-08-31 00:50:40 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,617,291 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w19w213w214w315w019w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db32935…81a7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xcf6fb232…dbca
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdbc6e634…e16c
0x1b6862…e19c
4 touches
1 conflict
0x0156f0d7…1df6
0x34b655…2a6f
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
6 conflicts on slot 0x8db3293548…c981a7
Audit this contract →
← previous block·next block →recent activity