← previous blocknext block →recent activity

Analyzing

Block #74,317,803

9 transactions · 9 stateful · 2026-05-13 12:11:49 UTC

Parallelism

56/100

Blocked

44%

Avg conflicts / tx

0.78

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,317,803  ·  9 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x64461c10…e86d

0x34b655…2a6f

8 touches
6 conflicts

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0x4e39aafd…796e

0x34b655…2a6f

6 touches
3 conflicts

0x9b1a47c3…69f8

0xde22b2…7777

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0xbf25e763…684f

0x3bd359…433a

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity