← previous blocknext block →recent activity
Analyzing
Block #103,222,251
14 transactions · 14 stateful · 2026-09-09 03:50:13 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,222,251 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x27aff880…894e
0x34b655…2a6f
4 touches
1 conflict
0x40dc5d65…9cbb
0x34b655…2a6f
4 touches
1 conflict
0x58b27dde…52d1
0x34b655…2a6f
4 touches
1 conflict
0x5ee1769f…2d59
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x8a377bad…474b
0x34b655…2a6f
4 touches
1 conflict
0x9421a154…d296
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
1 conflict on slot 0x167de262c8…3ef61f
Audit this contract →
← previous block·next block →recent activity