← previous blocknext block →recent activity
Analyzing
Block #101,019,898
26 transactions · 24 stateful · 2026-09-01 10:36:23 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,019,898 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w07w08w29w110w211w313w115w216w217w318w420w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
8 touches
6 conflicts
0xacd7220d…e389
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfe45073e…6315
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
6 conflicts on slot 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity