← previous blocknext block →recent activity

Analyzing

Block #73,977,740

18 transactions · 16 stateful · 2026-05-11 22:27:32 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,977,740  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x4128fc8a…d9aa

0xd32edf…ff58

11 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x6c66d3f7…ceee

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0000

0x139aab…382b

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 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

15 conflicts on slot 0x4128fc8a4f…21d9aa

← previous block·next block →recent activity