← previous blocknext block →recent activity
Analyzing
Block #106,538,079
21 transactions · 20 stateful · 2026-09-20 18:45:09 UTC
Parallelism
52/100
Blocked
60%
Avg conflicts / tx
2.48
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,538,079 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w07w19w210w311w112w413w414w515w616w717w818w920w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46a5ec6c…f318
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd41f5136…97c6
0x34b655…2a6f
14 touches
21 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
10 touches
10 conflicts
0xe098738f…9bbe
0x34b655…2a6f
10 touches
10 conflicts
0x04994ed2…9032
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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
45 conflicts on slot 0x46a5ec6cde…19f318
Audit this contract →
← previous block·next block →recent activity