← previous blocknext block →recent activity
Analyzing
Block #102,736,804
20 transactions · 18 stateful · 2026-09-07 11:01:59 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,736,804 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w010w113w214w317w018w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
8 touches
6 conflicts
0xd6de2989…db19
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe66201d4…84f1
0x34b655…2a6f
6 touches
3 conflicts
0x38cce915…c9a0
0x34b655…2a6f
6 touches
3 conflicts
0x890b77c0…379c
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity