← previous blocknext block →recent activity
Analyzing
Block #106,934,118
17 transactions · 17 stateful · 2026-09-22 03:59:27 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
1.82
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,934,118 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x73a0005f…70a8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x6b1259e6…4e12
0x1b6862…e19c
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
28 conflicts on slot 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity