← previous blocknext block →recent activity

Analyzing

Block #74,918,663

17 transactions · 12 stateful · 2026-05-16 07:03:50 UTC

Parallelism

59/100

Blocked

58%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,918,663  ·  17 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x01e7b865…6e6d

0x188d58…ea8e

12 touches
15 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x665b660b…b07e

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xf35dca9e…bd8d

0x1b6862…e19c

6 touches
3 conflicts

0x01e7b865…6e70

0x188d58…ea8e

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: 0x188d586d…f9ea8e

15 conflicts on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity