← previous blocknext block →recent activity
Analyzing
Block #106,569,852
20 transactions · 18 stateful · 2026-09-20 21:25:03 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,569,852 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w214w315w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5727953d…b240
0x34b655…2a6f
12 touches
15 conflicts
0x310a7246…2dcb
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0xafbbc9b5…1642
0x34b655…2a6f
8 touches
6 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
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
15 conflicts on slot 0x5727953d03…38b240
Audit this contract →
← previous block·next block →recent activity