← previous blocknext block →recent activity

Analyzing

Block #74,761,188

32 transactions · 25 stateful · 2026-05-15 13:32:58 UTC

Parallelism

56/100

Blocked

68%

Avg conflicts / tx

2.84

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #74,761,188  ·  32 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xa704b453…eae0

0xd32edf…ff58

25 touches
78 conflicts

0x0a85a226…83bc

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x524bd78c…8312

0x065c9d…c394

7 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

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

78 conflicts on slot 0xa704b453a2…05eae0

← previous block·next block →recent activity