← previous blocknext block →recent activity
Analyzing
Block #106,190,988
18 transactions · 18 stateful · 2026-09-19 13:38:13 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,190,988 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w09w111w012w114w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9ddc6d5…86a2
0x34b655…2a6f
8 touches
6 conflicts
0xd62f3741…b903
0x34b655…2a6f
8 touches
6 conflicts
0x708d7a74…09e3
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xd9ddc6d597…8d86a2
Audit this contract →
← previous block·next block →recent activity