← previous blocknext block →recent activity

Analyzing

Block #74,335,605

16 transactions · 15 stateful · 2026-05-13 14:10:07 UTC

Parallelism

44/100

Blocked

53%

Avg conflicts / tx

2.25

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,335,605  ·  16 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xbf25e763…684f

0x3bd359…433a

18 touches
36 conflicts

0x00000000…0000

0x776059…1d8d

18 touches
36 conflicts

0x00000000…0001

0x776059…1d8d

18 touches
36 conflicts

0x00000000…0003

0x776059…1d8d

18 touches
36 conflicts

0x9b1a47c3…69f8

0xde22b2…7777

18 touches
36 conflicts

0x9263d60a…a636

0x065c9d…c394

2 touches
0 conflicts

0xa7fdb62b…4310

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 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: 0x3bd359c1…15433a

36 conflicts on slot 0xbf25e763b6…db684f

← previous block·next block →recent activity