← previous blocknext block →recent activity

Analyzing

Block #74,646,907

28 transactions · 22 stateful · 2026-05-15 00:50:00 UTC

Parallelism

68/100

Blocked

55%

Avg conflicts / tx

1.32

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,646,907  ·  28 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

0x65ff3d9e…d9f4

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xfc3cb12e…c137

0x065c9d…c394

9 touches
10 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

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

21 conflicts on slot 0x65ff3d9e14…a6d9f4

← previous block·next block →recent activity