← previous blocknext block →recent activity

Analyzing

Block #74,252,773

8 transactions · 6 stateful · 2026-05-13 04:59:15 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,252,773  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x83ecdae3…50da

0x699abc…6a3b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x5fec5751…85f7

0x699abc…6a3b

3 touches
1 conflict

0x3817764d…242b

0x34b655…2a6f

2 touches
0 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

2 touches
0 conflicts

0x71e96b74…abe9

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: 0x34b6552d…112a6f

1 conflict on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity