← previous blocknext block →recent activity

Analyzing

Block #74,586,239

15 transactions · 9 stateful · 2026-05-14 18:04:47 UTC

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.13

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,586,239  ·  15 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

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0x816881fb…e436

0x34b655…2a6f

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x82754758…a06b

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xedf24d80…e2f6

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 0x5aed1bd252…0a7afa

← previous block·next block →recent activity