← previous blocknext block →recent activity

Analyzing

Block #74,899,482

40 transactions · 25 stateful · 2026-05-16 04:55:54 UTC

Parallelism

77/100

Blocked

48%

Avg conflicts / tx

0.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,899,482  ·  40 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

0x27d01e2c…58ee

0xd32edf…ff58

15 touches
28 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbfe7fd3a…3168

0x3bd359…433a

4 touches
1 conflict

0x22a828bf…8b10

0x5e0734…69c1

4 touches
1 conflict

0xbb371eab…3efc

0x5e0734…69c1

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x2d360b55…d4f5

0x80f006…d585

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 0x27d01e2cc0…5b58ee

← previous block·next block →recent activity