← previous blocknext block →recent activity
Analyzing
Block #103,221,903
13 transactions · 12 stateful · 2026-09-09 03:48:28 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #103,221,903 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x58b27dde…52d1
0x34b655…2a6f
6 touches
3 conflicts
0x9ee824ec…5faa
0x34b655…2a6f
5 touches
3 conflicts
0x5ee1769f…2d59
0x34b655…2a6f
4 touches
1 conflict
0x6c2d3b38…a21e
0x34b655…2a6f
4 touches
1 conflict
0x747f609d…1555
0x34b655…2a6f
4 touches
1 conflict
0x7adc097a…9a21
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity