← previous blocknext block →recent activity

Analyzing

Block #74,736,245

27 transactions · 22 stateful · 2026-05-15 10:46:11 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,736,245  ·  27 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

0xa38bcc95…58d2

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

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

28 conflicts on slot 0xa38bcc9545…7458d2

← previous block·next block →recent activity