← previous blocknext block →recent activity
Analyzing
Block #102,048,315
20 transactions · 20 stateful · 2026-09-05 00:56:40 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,048,315 · 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
1w02w03w14w25w37w08w19w013w114w115w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29a58269…011a
0x34b655…2a6f
8 touches
6 conflicts
0xa2c04336…e4c0
0x34b655…2a6f
8 touches
6 conflicts
0xa1a01ded…c087
0x34b655…2a6f
8 touches
6 conflicts
0x173b64af…6c43
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x4dffc33e…068d
0x34b655…2a6f
8 touches
6 conflicts
0x3d13406e…eff1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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 0x29a582695b…cf011a
Audit this contract →
← previous block·next block →recent activity