← previous blocknext block →recent activity
Analyzing
Block #107,630,838
21 transactions · 18 stateful · 2026-09-24 14:27:18 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,630,838 · 21 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
1w04w15w26w07w19w011w313w115w217w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51a94f0…f9b9
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x9a3420dc…8274
0x34b655…2a6f
4 touches
1 conflict
0xc49bec63…83d4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0xf51a94f02f…87f9b9
Audit this contract →
← previous block·next block →recent activity