← previous blocknext block →recent activity

Analyzing

Block #120,076,600

17 transactions · 16 stateful · 2026-11-07 03:48:20 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #120,076,600  ·  17 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

0xfd4e632c…e14c

0x34b655…2a6f

8 touches
6 conflicts

0xc2575a0e…f99b

0xf884c7…b285

6 touches
3 conflicts

0x40d6d1e9…131e

0x34b655…2a6f

4 touches
1 conflict

0xa2434b71…1910

0x34b655…2a6f

4 touches
1 conflict

0xb8acd6db…8581

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe946fc08…da77

0x34b655…2a6f

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: Perpl

6 conflicts on slot 0xfd4e632c76…e1e14c

← previous block·next block →recent activity