← previous blocknext block →recent activity
Analyzing
Block #107,817,312
21 transactions · 21 stateful · 2026-09-25 06:07:21 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,817,312 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w17w28w09w010w111w212w313w314w415w416w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
10 touches
10 conflicts
0xa5811d93…8c73
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x939cdd56…00c8
0x34b655…2a6f
8 touches
6 conflicts
0x0387011d…3814
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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
10 conflicts on slot 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity