← previous blocknext block →recent activity
Analyzing
Block #103,222,315
13 transactions · 13 stateful · 2026-09-09 03:50:32 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,222,315 · 13 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
1w02w13w25w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36aa792c…a68d
0x34b655…2a6f
6 touches
3 conflicts
0xe6d9c62e…465a
0x34b655…2a6f
6 touches
3 conflicts
0x0f13b598…f75b
0x34b655…2a6f
6 touches
3 conflicts
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x2bf68b1d…0d27
0x34b655…2a6f
4 touches
1 conflict
0x2d4b76b6…d903
0x34b655…2a6f
4 touches
1 conflict
0x34f8df0b…ad11
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
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 0x36aa792c6a…6da68d
Audit this contract →
← previous block·next block →recent activity