← previous blocknext block →recent activity
Analyzing
Block #102,235,218
16 transactions · 14 stateful · 2026-09-05 16:44:02 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,235,218 · 16 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
1w05w19w010w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a7af3fd…72a6
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
8 touches
6 conflicts
0xfb682e7d…dde9
0x34b655…2a6f
8 touches
6 conflicts
0xce749179…d29b
0x34b655…2a6f
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x252771a6…3918
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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 0x8a7af3fdbb…2b72a6
Audit this contract →
← previous block·next block →recent activity