← previous blocknext block →recent activity
Analyzing
Block #102,326,373
35 transactions · 28 stateful · 2026-09-06 00:26:00 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,326,373 · 35 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
4w06w07w111w014w115w216w317w018w125w226w327w433w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6f5e37…6c3c
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x212a19ca…2dd4
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xcc753ff7…6e65
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x0a6f5e3795…116c3c
Audit this contract →
← previous block·next block →recent activity