← previous blocknext block →recent activity
Analyzing
Block #120,413,281
16 transactions · 16 stateful · 2026-11-08 08:07:23 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #120,413,281 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w28w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x5ee3f950…32bf
0x264123…670e
6 touches
3 conflicts
0x8526d37e…0880
0xc9de99…405d
6 touches
3 conflicts
0x8526d37e…0881
0xc9de99…405d
6 touches
3 conflicts
0x8526d37e…0882
0xc9de99…405d
6 touches
3 conflicts
0xc2575a0e…f805
0xc9de99…405d
6 touches
3 conflicts
0xc2575a0e…f902
0xc9de99…405d
4 touches
1 conflict
0xd51d3055…e680
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: 0x125f12a1…cda50b
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity