← previous blocknext block →recent activity

Analyzing

Block #73,964,743

12 transactions · 7 stateful · 2026-05-11 21:00:31 UTC

Parallelism

67/100

Blocked

57%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,964,743  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0a8888a5…10a5

0xd32edf…ff58

7 touches
6 conflicts

0x81a7ba4d…8c4b

0x23c26b…7777

4 touches
1 conflict

0x08fdca0b…4abf

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x23c26b…7777

4 touches
1 conflict

0x00000000…0000

0xfdc9ea…8789

4 touches
1 conflict

0x00000000…0002

0xfdc9ea…8789

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x67d47cb1…3fa0

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

6 conflicts on slot 0x0a8888a532…f010a5

← previous block·next block →recent activity