← previous blocknext block →recent activity
Analyzing
Block #106,952,092
20 transactions · 20 stateful · 2026-09-22 05:29:56 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,952,092 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w17w28w39w112w013w115w316w417w518w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f887fbb…76d5
0x34b655…2a6f
8 touches
6 conflicts
0xce759540…68df
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
6 touches
3 conflicts
0xc35d158c…6271
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 0x2f887fbb5a…4076d5
Audit this contract →
← previous block·next block →recent activity