← previous blocknext block →recent activity
Analyzing
Block #107,848,714
24 transactions · 17 stateful · 2026-09-25 08:45:24 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,848,714 · 24 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
3w05w06w18w09w111w212w313w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba522812…1f1f
0x34b655…2a6f
8 touches
6 conflicts
0xf30b9357…2e1e
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
8 touches
6 conflicts
0x8f49a54c…e04c
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3fcf90a0…38a6
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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
6 conflicts on slot 0xba52281226…3a1f1f
Audit this contract →
← previous block·next block →recent activity