← previous blocknext block →recent activity

Analyzing

Block #74,427,399

19 transactions · 9 stateful · 2026-05-14 00:21:00 UTC

Parallelism

84/100

Blocked

22%

Avg conflicts / tx

0.11

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,427,399  ·  19 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x157d1e46…85f6

0x34b655…2a6f

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x62c7d955…093d

0x065c9d…c394

2 touches
0 conflicts

0x68d840fe…0ea9

0x065c9d…c394

2 touches
0 conflicts

0x68ecb5c4…a85c

0x065c9d…c394

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity