← previous blocknext block →recent activity

Analyzing

Block #74,403,340

10 transactions · 10 stateful · 2026-05-13 21:40:55 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,403,340  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x9b8800c1…ed12

0x34b655…2a6f

4 touches
1 conflict

0xa1d3789f…ab59

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbfca3cd0…5023

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xda1f3e2c…b73d

0x34b655…2a6f

4 touches
1 conflict

0x0de7749d…5bef

0x34b655…2a6f

4 touches
1 conflict

0x54fc792d…d33f

0x065c9d…c394

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

1 conflict on slot 0x9b8800c1a6…6ced12

← previous block·next block →recent activity