← previous blocknext block →recent activity
Analyzing
Block #101,896,493
26 transactions · 25 stateful · 2026-09-04 12:06:57 UTC
Parallelism
69/100
Blocked
68%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,896,493 · 26 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
1w02w13w24w05w17w39w110w111w212w314w416w517w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbf974a4…b232
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf10f9d72…32e0
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xcb13e63f…c6f8
0x34b655…2a6f
8 touches
6 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
8 touches
6 conflicts
0x56a4b8ae…8836
0x34b655…2a6f
8 touches
6 conflicts
0x08e8f2c9…a11a
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
10 conflicts on slot 0xdbf974a4cf…a9b232
Audit this contract →
← previous block·next block →recent activity