← previous blocknext block →recent activity
Analyzing
Block #120,413,464
22 transactions · 20 stateful · 2026-11-08 08:08:18 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #120,413,464 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w114w015w016w117w218w319w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18a04fbd…aab4
0x34b655…2a6f
8 touches
6 conflicts
0xe23bd67b…6a7e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe9b0f2f0…0a50
0x264123…670e
4 touches
1 conflict
0xfc01b950…c911
0x264123…670e
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x74dd7803…6d00
0x8121ee…ee7a
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
6 conflicts on slot 0x18a04fbdb4…e2aab4
Audit this contract →
← previous block·next block →recent activity