← previous blocknext block →recent activity
Analyzing
Block #101,061,399
30 transactions · 28 stateful · 2026-09-01 14:05:11 UTC
Parallelism
53/100
Blocked
68%
Avg conflicts / tx
1.97
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #101,061,399 · 30 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
1w02w13w04w18w09w110w011w212w313w415w216w317w419w520w122w624w825w926w1028w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x8d15d872…fa53
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x304f46e4…3f46
0x34b655…2a6f
6 touches
3 conflicts
0x45a62708…1f94
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity