← previous blocknext block →recent activity
Analyzing
Block #106,186,731
29 transactions · 28 stateful · 2026-09-19 13:16:48 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,186,731 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w26w37w49w112w224w425w527w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x854ce402…932a
0x34b655…2a6f
12 touches
15 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0xa6464996…3af9
0x34b655…2a6f
10 touches
10 conflicts
0xd597209e…9800
0x34b655…2a6f
10 touches
10 conflicts
0x360f08af…37a3
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xa499e820…5b2d
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 0x854ce4023f…96932a
Audit this contract →
← previous block·next block →recent activity