← previous blocknext block →recent activity
Analyzing
Block #103,221,917
13 transactions · 11 stateful · 2026-09-09 03:48:32 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,221,917 · 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
4w010w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x587dcf2c…7759
0x34b655…2a6f
4 touches
1 conflict
0x9ee824ec…5faa
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x2917f522…d1fe
0x34b655…2a6f
2 touches
0 conflicts
0x3c4cad5f…dfe2
0x34b655…2a6f
2 touches
0 conflicts
0x4318eb59…396b
0x34b655…2a6f
2 touches
0 conflicts
0x55e05c7a…0ab5
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
3 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity