← previous blocknext block →recent activity

Analyzing

Block #74,284,587

8 transactions · 8 stateful · 2026-05-13 08:30:46 UTC

Parallelism

63/100

Blocked

25%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,284,587  ·  8 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xc12b04b0…884b

0x34b655…2a6f

4 touches
1 conflict

0x5aed1bd2…7afa

0x34b655…2a6f

4 touches
1 conflict

0xfe3b9476…2e67

0x34b655…2a6f

4 touches
1 conflict

0x4b268018…02fb

0x34b655…2a6f

4 touches
1 conflict

0x47464fbb…c429

0x34b655…2a6f

2 touches
0 conflicts

0x5d99a6e0…be0e

0x34b655…2a6f

2 touches
0 conflicts

0x6a15f784…10b2

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity