← previous blocknext block →recent activity

Analyzing

Block #73,987,181

20 transactions · 17 stateful · 2026-05-11 23:30:59 UTC

Parallelism

55/100

Blocked

59%

Avg conflicts / tx

1.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,987,181  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x334dd4dc…45d8

0x34b655…2a6f

2 touches
0 conflicts

0x336241b2…c1db

0x34b655…2a6f

2 touches
0 conflicts

0x4bedb8a9…81cc

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

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity