← previous blocknext block →recent activity

Analyzing

Block #74,346,646

23 transactions · 11 stateful · 2026-05-13 15:23:36 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.26

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,346,646  ·  23 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

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

4 touches
1 conflict

0xac8e97a0…8426

0x34b655…2a6f

4 touches
1 conflict

0xdab59320…142d

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xfd76de76…e011

0x5c2513…7777

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity