← previous blocknext block →recent activity

Analyzing

Block #74,765,064

15 transactions · 11 stateful · 2026-05-15 13:58:56 UTC

Parallelism

67/100

Blocked

55%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,765,064  ·  15 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x84fb2a36…db89

0x34b655…2a6f

6 touches
3 conflicts

0xf210fbba…ab2c

0xd32edf…ff58

5 touches
3 conflicts

0x7b6d2deb…dde0

0x34b655…2a6f

4 touches
1 conflict

0x145554b9…8b5f

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity