← previous blocknext block →recent activity

Analyzing

Block #74,644,018

18 transactions · 15 stateful · 2026-05-15 00:30:46 UTC

Parallelism

50/100

Blocked

67%

Avg conflicts / tx

1.78

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,644,018  ·  18 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

0x451e3c05…a33a

0xd32edf…ff58

15 touches
28 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x17a7f697…dcb8

0x1b6862…e19c

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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 0x451e3c0581…72a33a

← previous block·next block →recent activity