← previous blocknext block →recent activity
Analyzing
Block #120,114,303
18 transactions · 17 stateful · 2026-11-07 06:58:24 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #120,114,303 · 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
2w03w04w16w07w18w115w016w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x33ef7909…fc8e
0x264123…670e
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x1978ca4a…10e3
0x34b655…2a6f
4 touches
1 conflict
0x2dd8b93a…54b5
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x215a6452…18ae
0x264123…670e
2 touches
0 conflicts
0x5ee3f950…32bf
0x264123…670e
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity