← previous blocknext block →recent activity
Analyzing
Block #106,934,617
19 transactions · 18 stateful · 2026-09-22 04:01:58 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,934,617 · 19 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
1w02w16w07w18w29w310w111w312w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
14 touches
21 conflicts
0xfb7455b6…deca
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0xf6f478d1…7442
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x04994ed2…9032
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
6 touches
3 conflicts
0xa0edadb9…dbfe
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
21 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity