← previous blocknext block →recent activity
Analyzing
Block #120,077,047
20 transactions · 16 stateful · 2026-11-07 03:50:35 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #120,077,047 · 20 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
1w03w07w08w114w115w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
8 touches
6 conflicts
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0xd739490d…821e
0x34b655…2a6f
8 touches
6 conflicts
0xfd808de1…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0x23ef1567…8f31
0x34b655…2a6f
6 touches
3 conflicts
0x3c4f7092…9680
0xed3727…f3af
4 touches
1 conflict
0x947d8e81…ffeb
0x264123…670e
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity