← previous blocknext block →recent activity
Analyzing
Block #106,200,520
21 transactions · 21 stateful · 2026-09-19 14:26:12 UTC
Parallelism
62/100
Blocked
57%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,200,520 · 21 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
1w02w13w24w05w16w27w38w410w414w515w619w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61cd438d…536f
0x34b655…2a6f
12 touches
15 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd8d828a7…b64e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x61cd438db3…11536f
Audit this contract →
← previous block·next block →recent activity