← previous blocknext block →recent activity
Analyzing
Block #106,356,683
35 transactions · 34 stateful · 2026-09-20 03:32:11 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,356,683 · 35 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w012w013w115w016w117w118w219w021w123w329w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe868178d…79ad
0x34b655…2a6f
6 touches
3 conflicts
0xca2766a9…f268
0xd32edf…ff58
5 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x21e79ad8…c5db
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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
3 conflicts on slot 0xe868178d92…3179ad
Audit this contract →
← previous block·next block →recent activity