← previous blocknext block →recent activity
Analyzing
Block #102,569,263
17 transactions · 17 stateful · 2026-09-06 20:57:05 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,569,263 · 17 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
4w06w17w08w110w211w312w313w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x072c7ca8…604d
0x34b655…2a6f
8 touches
6 conflicts
0x56f13663…8d31
0x34b655…2a6f
8 touches
6 conflicts
0x9a9383a9…6bc7
0x34b655…2a6f
6 touches
3 conflicts
0xbbc4bdf7…c62f
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 0x24ed74ea30…24a3ff
Audit this contract →
← previous block·next block →recent activity