← previous blocknext block →recent activity
Analyzing
Block #107,613,528
14 transactions · 12 stateful · 2026-09-24 12:59:54 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,613,528 · 14 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
1w03w15w28w09w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06d6349e…686d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x2cf99f8c…5f1e
0x34b655…2a6f
4 touches
1 conflict
0x4856b443…1824
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
4 touches
1 conflict
0xb92126c1…5384
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
1 conflict on slot 0x06d6349e00…18686d
Audit this contract →
← previous block·next block →recent activity