← previous blocknext block →recent activity
Analyzing
Block #119,856,259
15 transactions · 14 stateful · 2026-11-06 09:14:20 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #119,856,259 · 15 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
1w05w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6c48940d…5f80
0xf884c7…b285
4 touches
1 conflict
0x6c48940d…5f81
0xf884c7…b285
4 touches
1 conflict
0xc2575a0e…f805
0xf884c7…b285
4 touches
1 conflict
0xc2575a0e…f996
0xf884c7…b285
4 touches
1 conflict
0x9a2a3d9d…729e
0x264123…670e
2 touches
0 conflicts
0xd6473d14…a5ee
0x264123…670e
2 touches
0 conflicts
0x816d0352…a531
0x39fded…dfb2
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: Perpl
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity