← previous blocknext block →recent activity
Analyzing
Block #106,958,684
27 transactions · 24 stateful · 2026-09-22 06:03:07 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,958,684 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w39w413w515w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x9cc9cd65…7dae
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0x1c59817b…07e8
0x34b655…2a6f
4 touches
1 conflict
0x01ad5dd0…11a1
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity