← previous blocknext block →recent activity

Analyzing

Block #74,241,648

20 transactions · 17 stateful · 2026-05-13 03:45:18 UTC

Parallelism

70/100

Blocked

53%

Avg conflicts / tx

1.25

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,241,648  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x536e2740…61ac

0x3bd359…433a

10 touches
10 conflicts

0x635321e6…3124

0xa7283d…0ace

10 touches
10 conflicts

0x635321e6…3123

0xa7283d…0ace

10 touches
10 conflicts

0x635321e6…3125

0xa7283d…0ace

10 touches
10 conflicts

0x00000000…0002

0xa7283d…0ace

10 touches
10 conflicts

0x8fa7a69c…8fd7

0x46bd38…7777

10 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity