← previous blocknext block →recent activity

Analyzing

Block #74,637,314

30 transactions · 22 stateful · 2026-05-14 23:46:07 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,637,314  ·  30 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

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0xded5ec0c…f0fc

0x34b655…2a6f

6 touches
3 conflicts

0x3eadb0b6…d2f7

0x34b655…2a6f

6 touches
3 conflicts

0xd390f95d…b72c

0xd32edf…ff58

5 touches
3 conflicts

0x2905340c…dbc6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity