← previous blocknext block →recent activity

Analyzing

Block #74,333,498

29 transactions · 26 stateful · 2026-05-13 13:56:08 UTC

Parallelism

48/100

Blocked

65%

Avg conflicts / tx

3.76

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #74,333,498  ·  29 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

0xd004cf…da29

30 touches
105 conflicts

0xaf7c2ffc…5a6f

0x3bd359…433a

30 touches
105 conflicts

0xdbde8233…3e76

0xdb8585…7777

30 touches
105 conflicts

0x00000000…0000

0xd004cf…da29

30 touches
105 conflicts

0x00000000…0003

0xd004cf…da29

30 touches
105 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x664bf99e…0a8c

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: 0xd004cfed…42da29

105 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity