← previous blocknext block →recent activity

Analyzing

Block #73,696,195

39 transactions · 33 stateful · 2026-05-10 15:02:46 UTC

Parallelism

85/100

Blocked

48%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,696,195  ·  39 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0eeb2294…3a12

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity