← previous blocknext block →recent activity
Analyzing
Block #106,100,105
27 transactions · 26 stateful · 2026-09-19 06:00:51 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,100,105 · 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
1w02w03w19w010w112w013w118w120w123w224w325w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xcfe180d7…b5a4
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity