← previous blocknext block →recent activity
Analyzing
Block #102,742,123
21 transactions · 15 stateful · 2026-09-07 11:28:45 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,742,123 · 21 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
1w02w13w010w211w217w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x014e90b3…470f
0x34b655…2a6f
8 touches
6 conflicts
0x10a5a231…be40
0x34b655…2a6f
6 touches
3 conflicts
0xb11fef8e…9f7c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe4d0d642…b038
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xa169711f…c7f3
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
6 conflicts on slot 0x014e90b366…e0470f
Audit this contract →
← previous block·next block →recent activity