← previous blocknext block →recent activity
Analyzing
Block #106,931,715
15 transactions · 14 stateful · 2026-09-22 03:47:22 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,931,715 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ddef8d6…636b
0x34b655…2a6f
10 touches
10 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
6 touches
3 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x858e40c0…7e30
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x21d8e673…067e
0x1b6862…e19c
4 touches
1 conflict
0xd9a74048…63af
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
10 conflicts on slot 0x7ddef8d6ee…8d636b
Audit this contract →
← previous block·next block →recent activity