← previous blocknext block →recent activity

Analyzing

Block #73,035,100

33 transactions · 29 stateful · 2026-05-07 13:38:08 UTC

Parallelism

55/100

Blocked

76%

Avg conflicts / tx

3.76

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #73,035,100  ·  33 txs across 15 waves  ·  depth 15
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

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

0xd574ca…7ab1

30 touches
105 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x5be153c8…6d9e

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x17e2d2a0…359e

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: 0xd574cae5…037ab1

105 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity