← previous blocknext block →recent activity
Analyzing
Block #101,895,785
19 transactions · 18 stateful · 2026-09-04 12:03:22 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,895,785 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w27w38w09w110w213w315w417w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59d2df30…aff2
0x34b655…2a6f
8 touches
6 conflicts
0xa67f91fa…bfd3
0x34b655…2a6f
6 touches
3 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 conflicts
0xc0a73ae2…2e95
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x898a08aa…c855
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 0x59d2df3068…cbaff2
Audit this contract →
← previous block·next block →recent activity