← previous blocknext block →recent activity

Analyzing

Block #74,333,662

25 transactions · 23 stateful · 2026-05-13 13:57:14 UTC

Parallelism

44/100

Blocked

61%

Avg conflicts / tx

3.68

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #74,333,662  ·  25 txs across 14 waves  ·  depth 14
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

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

0xd004cf…da29

28 touches
91 conflicts

0x00000000…0001

0xd004cf…da29

28 touches
91 conflicts

0x00000000…0003

0xd004cf…da29

28 touches
91 conflicts

0xdbde8233…3e76

0xdb8585…7777

28 touches
91 conflicts

0xaf7c2ffc…5a6f

0x3bd359…433a

28 touches
91 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x73a69d96…939d

0xdb8585…7777

2 touches
0 conflicts

0x937d187e…e650

0xdb8585…7777

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

91 conflicts on slot 0x0000000000…000000

← previous block·next block →recent activity