← previous blocknext block →recent activity
Analyzing
Block #106,109,714
24 transactions · 22 stateful · 2026-09-19 06:49:12 UTC
Parallelism
54/100
Blocked
64%
Avg conflicts / tx
2.42
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,109,714 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w39w411w414w515w616w717w818w921w523w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4d37162…967c
0x34b655…2a6f
16 touches
28 conflicts
0x740e8901…f572
0x34b655…2a6f
12 touches
15 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
10 touches
10 conflicts
0x6acea22a…1cc6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
8 touches
6 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0xa4d371626a…aa967c
Audit this contract →
← previous block·next block →recent activity