← previous blocknext block →recent activity
Analyzing
Block #106,542,405
19 transactions · 18 stateful · 2026-09-20 19:06:56 UTC
Parallelism
58/100
Blocked
39%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,542,405 · 19 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
1w02w19w210w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71943d07…69fe
0x34b655…2a6f
16 touches
28 conflicts
0x735a86cd…b64d
0x34b655…2a6f
10 touches
10 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0xf788c790…e66f
0x34b655…2a6f
6 touches
3 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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
28 conflicts on slot 0x71943d0702…9069fe
Audit this contract →
← previous block·next block →recent activity