← previous blocknext block →recent activity

Analyzing

Block #74,803,897

33 transactions · 24 stateful · 2026-05-15 18:18:27 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,803,897  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x630d2171…a098

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x718ae7bf…c9bc

0xc8689a…ee79

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

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: 0xd32edf66…9fff58

15 conflicts on slot 0x630d2171ea…06a098

← previous block·next block →recent activity