← previous blocknext block →recent activity
Analyzing
Block #119,285,572
18 transactions · 16 stateful · 2026-11-04 09:00:48 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #119,285,572 · 18 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
3w04w05w16w19w210w311w312w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2575a0e…f914
0xc9de99…405d
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xc2575a0e…f805
0xc9de99…405d
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x816d0352…a531
0xbe5ca1…e33b
4 touches
1 conflict
0x13f390f2…7980
0xc9de99…405d
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: 0xc9de998e…86405d
6 conflicts on slot 0xc2575a0e9e…71f914
Audit this contract →
← previous block·next block →recent activity