← previous blocknext block →recent activity
Analyzing
Block #101,060,912
36 transactions · 34 stateful · 2026-09-01 14:02:44 UTC
Parallelism
61/100
Blocked
62%
Avg conflicts / tx
1.75
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #101,060,912 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w17w19w010w111w012w213w314w115w216w318w319w420w522w625w126w229w730w835w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x9c83a7b1…e305
0x34b655…2a6f
8 touches
6 conflicts
0x556a9a7a…b0ae
0x34b655…2a6f
8 touches
6 conflicts
0x261261a7…616e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0dd3d3cd…7281
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