← previous blocknext block →recent activity

Analyzing

Block #74,389,278

33 transactions · 23 stateful · 2026-05-13 20:07:17 UTC

Parallelism

82/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,389,278  ·  33 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

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x9b1a47c3…69f8

0xde22b2…7777

4 touches
1 conflict

0x44ad89ba…cf83

0x5e1b1a…7777

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

0x00000000…0000

0x75c3ab…4f0d

4 touches
1 conflict

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x00000000…0000

0x776059…1d8d

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity