← previous blocknext block →recent activity
Analyzing
Block #119,295,916
13 transactions · 13 stateful · 2026-11-04 09:53:08 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #119,295,916 · 13 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
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33ef7909…fc8e
0x264123…670e
4 touches
1 conflict
0x666889a7…968f
0x264123…670e
4 touches
1 conflict
0xab07df27…2647
0x264123…670e
4 touches
1 conflict
0x5a82a1d9…4100
0xc9de99…405d
4 touches
1 conflict
0x5a82a1d9…4101
0xc9de99…405d
4 touches
1 conflict
0xc2575a0e…f805
0xc9de99…405d
4 touches
1 conflict
0xc2575a0e…f912
0xc9de99…405d
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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: 0x264123a9…fa670e
1 conflict on slot 0x33ef79099b…f8fc8e
Audit this contract →
← previous block·next block →recent activity