← previous blocknext block →recent activity
Analyzing
Block #106,395,575
32 transactions · 28 stateful · 2026-09-20 06:47:55 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,395,575 · 32 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
1w02w13w24w05w16w17w28w316w421w522w623w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
8 touches
6 conflicts
0x79be5e7e…46b4
0x34b655…2a6f
8 touches
6 conflicts
0x8d664414…3344
0x34b655…2a6f
8 touches
6 conflicts
0xa8531704…5a2e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdd882484…aaa4
0x34b655…2a6f
8 touches
6 conflicts
0x17953a45…96a1
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
6 conflicts on slot 0x5d1ac445db…e05233
Audit this contract →
← previous block·next block →recent activity