← previous blocknext block →recent activity

Analyzing

Block #74,471,408

43 transactions · 27 stateful · 2026-05-14 05:13:57 UTC

Parallelism

81/100

Blocked

52%

Avg conflicts / tx

0.91

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,471,408  ·  43 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

0x972b91ec…f3c2

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

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 0x972b91ec8a…80f3c2

← previous block·next block →recent activity