← previous blocknext block →recent activity

Analyzing

Block #74,422,784

36 transactions · 26 stateful · 2026-05-13 23:50:16 UTC

Parallelism

83/100

Blocked

46%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,422,784  ·  36 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0xc8156aec…ce62

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

5 touches
3 conflicts

0x77ab5baf…002f

0xd32edf…ff58

5 touches
3 conflicts

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

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: 0x34b6552d…112a6f

15 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity