← previous blocknext block →recent activity
Analyzing
Block #112,612,129
23 transactions · 20 stateful · 2026-10-12 00:30:25 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #112,612,129 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w19w213w014w116w217w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xfa4630d4…3846
0x34b655…2a6f
12 touches
15 conflicts
0xb4656137…5858
0x34b655…2a6f
10 touches
10 conflicts
0x8c211514…b757
0x34b655…2a6f
8 touches
6 conflicts
0xc4550172…3d03
0x34b655…2a6f
6 touches
3 conflicts
0x1972739d…a40b
0x34b655…2a6f
6 touches
3 conflicts
0x2b31b795…80a0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity