← previous blocknext block →recent activity
Analyzing
Block #101,837,351
22 transactions · 22 stateful · 2026-09-04 07:09:12 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.23
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,837,351 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w49w010w113w015w217w318w420w221w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x663784e7…acb8
0x34b655…2a6f
10 touches
10 conflicts
0xe0da07e4…ccf2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x8d616e7c…a6a1
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xf36124ad…c08f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
8 touches
6 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 0x663784e73e…28acb8
Audit this contract →
← previous block·next block →recent activity