← previous blocknext block →recent activity
Analyzing
Block #121,859,407
33 transactions · 30 stateful · 2026-11-13 10:13:39 UTC
Parallelism
91/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #121,859,407 · 33 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
3w04w16w07w18w09w110w011w112w013w118w222w023w129w030w031w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8526d50…eadc
0x264123…670e
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x157d0d1d…3df2
0x264123…670e
4 touches
1 conflict
0x7003a7a5…94b5
0x264123…670e
4 touches
1 conflict
0x7ff69c25…f18f
0x264123…670e
4 touches
1 conflict
0x816d0352…a531
0x9cd7a2…d1a8
4 touches
1 conflict
0x12f4c605…4100
0xae8e0c…e422
4 touches
1 conflict
0x12f4c605…4101
0xae8e0c…e422
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: 0x264123a9…fa670e
3 conflicts on slot 0xc8526d50f8…a1eadc
Audit this contract →
← previous block·next block →recent activity