← previous blocknext block →recent activity

Analyzing

Block #73,869,084

14 transactions · 12 stateful · 2026-05-11 10:23:45 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,869,084  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x1414f3…5137

14 touches
21 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa8d

0x34b655…2a6f

2 touches
0 conflicts

0x22863bf9…19df

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: 0x1414f3ba…045137

21 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity