← previous blocknext block →recent activity

Analyzing

Block #74,390,443

30 transactions · 26 stateful · 2026-05-13 20:15:01 UTC

Parallelism

70/100

Blocked

62%

Avg conflicts / tx

1.67

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,390,443  ·  30 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

0x00000000…0002

0xab3526…fa38

18 touches
36 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x4582e32d…1abe

0x34b655…2a6f

4 touches
1 conflict

0x8fdebdb1…d449

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

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: 0xab35264b…1cfa38

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity