← previous blocknext block →recent activity
Analyzing
Block #100,851,396
27 transactions · 27 stateful · 2026-08-31 20:28:43 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,851,396 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w08w310w112w015w316w121w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51cfbcbc…fa29
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
6 touches
3 conflicts
0x0342318b…bae7
0x34b655…2a6f
4 touches
1 conflict
0x3939f94e…1cbc
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
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
10 conflicts on slot 0x51cfbcbcae…65fa29
Audit this contract →
← previous block·next block →recent activity