← previous blocknext block →recent activity

Analyzing

Block #118,537,993

18 transactions · 16 stateful · 2026-11-01 18:11:00 UTC

Parallelism

89/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #118,537,993  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x886f7fe6…8b7a

0x34b655…2a6f

4 touches
1 conflict

0x947d8e81…ffeb

0x264123…670e

4 touches
1 conflict

0x728f999a…832f

0x34b655…2a6f

4 touches
1 conflict

0x4dff85d0…0080

0xed3727…f3af

4 touches
1 conflict

0x4dff85d0…0081

0xed3727…f3af

4 touches
1 conflict

0x4dff85d0…0082

0xed3727…f3af

4 touches
1 conflict

0x4dff85d0…0083

0xed3727…f3af

4 touches
1 conflict

0xc2575a0e…f8f8

0xed3727…f3af

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

1 conflict on slot 0x886f7fe654…c88b7a

← previous block·next block →recent activity