← previous blocknext block →recent activity
Analyzing
Block #120,726,188
22 transactions · 22 stateful · 2026-11-09 10:26:50 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #120,726,188 · 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
2w03w14w25w06w18w09w110w211w012w113w218w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x02fe82…aa96
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x013bb37b…eb4a
0x1b6862…e19c
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x816d0352…a531
0xbe5ca1…e33b
6 touches
3 conflicts
0x30472227…5d80
0xc9de99…405d
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xb6d8b9e7…3ba8
0xd32edf…ff58
5 touches
3 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: 0x02fe828a…a3aa96
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity