← previous blocknext block →recent activity

Analyzing

Block #74,248,481

7 transactions · 7 stateful · 2026-05-13 04:30:46 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,248,481  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x73f4551d…4188

0x34b655…2a6f

4 touches
1 conflict

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x7f38bfbc…61e3

0x34b655…2a6f

4 touches
1 conflict

0x4fa34364…e1ee

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x316f911e…a920

0x34b655…2a6f

2 touches
0 conflicts

0x3817764d…242b

0x34b655…2a6f

2 touches
0 conflicts

0x59a54ff4…d21b

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 0x73f4551d9b…8a4188

← previous block·next block →recent activity