← previous blocknext block →recent activity
Analyzing
Block #120,396,311
10 transactions · 9 stateful · 2026-11-08 06:41:44 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #120,396,311 · 10 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x666889a7…968f
0x264123…670e
4 touches
1 conflict
0xb6c61a84…8f01
0xae8e0c…e422
4 touches
1 conflict
0xc8526d50…eadc
0x264123…670e
4 touches
1 conflict
0x1fbc1dd7…85ad
0x264123…670e
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
2 touches
0 conflicts
0x6235638c…6438
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
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: 0x264123a9…fa670e
1 conflict on slot 0x666889a7e2…ac968f
Audit this contract →
← previous block·next block →recent activity