← previous blocknext block →recent activity
Analyzing
Block #106,395,336
19 transactions · 19 stateful · 2026-09-20 06:46:43 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,395,336 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w07w111w013w214w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd563f3a1…94b1
0x34b655…2a6f
6 touches
3 conflicts
0xa2df21ed…9f1d
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x25bd380f…a658
0x34b655…2a6f
4 touches
1 conflict
0x3279ac03…03c4
0x34b655…2a6f
4 touches
1 conflict
0x4b1ed7eb…9ec1
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
3 conflicts on slot 0xd563f3a18c…f494b1
Audit this contract →
← previous block·next block →recent activity