← previous blocknext block →recent activity
Analyzing
Block #106,916,076
18 transactions · 18 stateful · 2026-09-22 02:28:39 UTC
Parallelism
61/100
Blocked
78%
Avg conflicts / tx
1.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,916,076 · 18 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
1w02w13w14w05w16w27w38w19w210w411w512w613w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5c7c6aa…fdba
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x158cd73a…d47b
0x34b655…2a6f
10 touches
10 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0xe6a595bf…3c45
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0xb5c7c6aad4…acfdba
Audit this contract →
← previous block·next block →recent activity