← previous blocknext block →recent activity

Analyzing

Block #73,991,569

13 transactions · 11 stateful · 2026-05-12 00:00:38 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,991,569  ·  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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x47185b3a…8f4f

0x065c9d…c394

2 touches
0 conflicts

0xc5b5128a…c5b2

0x065c9d…c394

2 touches
0 conflicts

0x79c6b715…c58b

0x57ea24…2cec

2 touches
0 conflicts

0xbbd96e4f…d11f

0x57ea24…2cec

2 touches
0 conflicts

0x63d273cc…f2ec

0x80f006…d585

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity