← previous blocknext block →recent activity

Analyzing

Block #74,010,422

13 transactions · 12 stateful · 2026-05-12 02:07:26 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,010,422  ·  13 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4284404e…1929

0x065c9d…c394

4 touches
1 conflict

0xfa54bbb0…a260

0x065c9d…c394

3 touches
1 conflict

0xc05e5564…5bb2

0x065c9d…c394

3 touches
1 conflict

0x06a1132b…feb4

0x34b655…2a6f

2 touches
0 conflicts

0x20299510…1261

0x34b655…2a6f

2 touches
0 conflicts

0x25de453d…9573

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity