← previous blocknext block →recent activity
Analyzing
Block #106,189,556
29 transactions · 25 stateful · 2026-09-19 13:31:01 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,189,556 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w07w08w110w011w012w115w116w217w121w022w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4a7a714…c8d5
0x34b655…2a6f
8 touches
6 conflicts
0xd41f5136…97c6
0x34b655…2a6f
8 touches
6 conflicts
0x05e1eba1…6491
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
0x34b655…2a6f
6 touches
3 conflicts
0x755c7b95…9404
0x34b655…2a6f
4 touches
1 conflict
0x794deb74…8253
0x34b655…2a6f
4 touches
1 conflict
0xb654bd89…a83b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0xd4a7a71423…b7c8d5
Audit this contract →
← previous block·next block →recent activity