← previous blocknext block →recent activity
Analyzing
Block #103,222,629
22 transactions · 18 stateful · 2026-09-09 03:52:07 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,222,629 · 22 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
4w011w012w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x0915887d…c917
0x34b655…2a6f
2 touches
0 conflicts
0x0ca1584a…ce79
0x34b655…2a6f
2 touches
0 conflicts
0x0e216931…58c3
0x34b655…2a6f
2 touches
0 conflicts
0x0f13b598…f75b
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity