← previous blocknext block →recent activity

Analyzing

Block #74,403,285

23 transactions · 21 stateful · 2026-05-13 21:40:33 UTC

Parallelism

70/100

Blocked

57%

Avg conflicts / tx

1.39

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,403,285  ·  23 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

0xf9da2e00…a63d

0xe9afa1…7777

14 touches
21 conflicts

0x00000000…0001

0x97805d…bb07

14 touches
21 conflicts

0x00000000…0000

0x97805d…bb07

14 touches
21 conflicts

0xc701ef68…587b

0x3bd359…433a

14 touches
21 conflicts

0x00000000…0003

0x97805d…bb07

14 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 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: 0xe9afa192…617777

21 conflicts on slot 0xf9da2e00ac…88a63d

← previous block·next block →recent activity