← previous blocknext block →recent activity
Analyzing
Block #102,233,973
24 transactions · 22 stateful · 2026-09-05 16:37:44 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,233,973 · 24 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
2w05w06w113w114w217w318w419w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
8 touches
6 conflicts
0x9298c308…6e8c
0x34b655…2a6f
7 touches
6 conflicts
0xbceecf11…0120
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity