← previous blocknext block →recent activity

Analyzing

Block #119,856,263

26 transactions · 21 stateful · 2026-11-06 09:14:21 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #119,856,263  ·  26 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xeddb6c44…d47e

0x34b655…2a6f

6 touches
3 conflicts

0xfd4e632c…e14c

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xf9f8a78a…25f3

0x34b655…2a6f

4 touches
1 conflict

0xd5d51054…32f0

0x264123…670e

2 touches
0 conflicts

0x816d0352…a531

0x4b1452…4802

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

← previous block·next block →recent activity