← previous blocknext block →recent activity
Analyzing
Block #102,491,930
26 transactions · 21 stateful · 2026-09-06 14:24:51 UTC
Parallelism
88/100
Blocked
43%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,491,930 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w010w112w013w116w018w120w221w122w225w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247cfb80…cca8
0x34b655…2a6f
6 touches
3 conflicts
0x76134d08…b40d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x247cfb80ae…c4cca8
Audit this contract →
← previous block·next block →recent activity