← previous blocknext block →recent activity
Analyzing
Block #106,538,567
15 transactions · 13 stateful · 2026-09-20 18:47:37 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,538,567 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w212w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a4b8ae…8836
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x80fdc5be…7070
0x34b655…2a6f
6 touches
3 conflicts
0xd6b9b85a…f729
0x34b655…2a6f
6 touches
3 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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
6 conflicts on slot 0x56a4b8ae55…d38836
Audit this contract →
← previous block·next block →recent activity