← previous blocknext block →recent activity

Analyzing

Block #74,684,840

20 transactions · 15 stateful · 2026-05-15 05:03:13 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,684,840  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xa02838a3…bc54

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x5ffc25fa…b119

0x34b655…2a6f

8 touches
6 conflicts

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0x070a562a…8147

0x34b655…2a6f

4 touches
2 conflicts

0x9a291a56…9a9c

0x34b655…2a6f

4 touches
1 conflict

0xcda9bc1f…69dc

0x34b655…2a6f

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

10 conflicts on slot 0xa02838a385…ffbc54

← previous block·next block →recent activity