← previous blocknext block →recent activity
Analyzing
Block #106,934,254
31 transactions · 30 stateful · 2026-09-22 04:00:08 UTC
Parallelism
84/100
Blocked
57%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,934,254 · 31 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
2w03w14w25w16w07w08w112w013w114w215w016w117w218w219w322w123w424w325w126w329w230w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7439eba…a7d8
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x9f27e173…a241
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0008
0xf3c9d0…3534
6 touches
3 conflicts
0x7fc8f46e…0f75
0x34b655…2a6f
6 touches
3 conflicts
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 0xa7439ebaf9…e3a7d8
Audit this contract →
← previous block·next block →recent activity