← previous blocknext block →recent activity

Analyzing

Block #74,774,971

12 transactions · 10 stateful · 2026-05-15 15:05:20 UTC

Parallelism

58/100

Blocked

40%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,774,971  ·  12 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

0x3e49348b…9445

0x34b655…2a6f

10 touches
10 conflicts

0x7cee1be1…e770

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0b712007…32d9

0x34b655…2a6f

6 touches
3 conflicts

0x62d6e82b…a750

0x34b655…2a6f

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x11f25e19…8bb1

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 0x3e49348b38…839445

← previous block·next block →recent activity