← previous blocknext block →recent activity

Analyzing

Block #73,921,131

12 transactions · 11 stateful · 2026-05-11 16:10:29 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,921,131  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xaa3492db…3703

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xf9470055…bbf8

0x34b655…2a6f

4 touches
1 conflict

0x0da492a3…44a5

0x34b655…2a6f

2 touches
0 conflicts

0x1a51d014…7836

0x34b655…2a6f

2 touches
0 conflicts

0x2dd1db0e…9269

0x34b655…2a6f

2 touches
0 conflicts

0x696cb728…4526

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 0xaa3492db13…fc3703

← previous block·next block →recent activity