← previous blocknext block →recent activity

Analyzing

Block #74,761,202

40 transactions · 30 stateful · 2026-05-15 13:33:04 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

1.27

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,761,202  ·  40 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3a490026…4851

0xd32edf…ff58

15 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

6 touches
3 conflicts

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

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

28 conflicts on slot 0x3a490026d4…aa4851

← previous block·next block →recent activity