← previous blocknext block →recent activity
Analyzing
Block #103,212,124
24 transactions · 24 stateful · 2026-09-09 02:59:12 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,212,124 · 24 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
1w02w13w28w210w011w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b924b5c…2ae5
0x34b655…2a6f
6 touches
3 conflicts
0x03f08d80…0661
0x34b655…2a6f
4 touches
1 conflict
0x18cf84a6…09e4
0x34b655…2a6f
4 touches
1 conflict
0x2905ed39…1865
0x34b655…2a6f
4 touches
1 conflict
0x2c45dc1d…9eca
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x4282d9b8…d7d9
0x34b655…2a6f
4 touches
1 conflict
0x4a1733b9…f6e6
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 0x9b924b5c04…242ae5
Audit this contract →
← previous block·next block →recent activity