← previous blocknext block →recent activity
Analyzing
Block #106,273,413
37 transactions · 32 stateful · 2026-09-19 20:33:09 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,273,413 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w522w423w624w729w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c47b1c…93c8
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
8 touches
6 conflicts
0xfaa2c379…6b11
0x34b655…2a6f
8 touches
6 conflicts
0x24ba3de1…d92d
0x34b655…2a6f
8 touches
6 conflicts
0x73baefc6…11a8
0x34b655…2a6f
8 touches
6 conflicts
0x94dabb65…43a3
0x34b655…2a6f
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
21 conflicts on slot 0x07c47b1ce2…b693c8
Audit this contract →
← previous block·next block →recent activity