← previous blocknext block →recent activity
Analyzing
Block #106,370,559
23 transactions · 22 stateful · 2026-09-20 04:42:00 UTC
Parallelism
70/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,370,559 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w010w011w112w113w219w320w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x709f93e6…4090
0xd32edf…ff58
5 touches
3 conflicts
0x46c14e01…ff09
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity