← previous blocknext block →recent activity

Analyzing

Block #74,782,813

18 transactions · 13 stateful · 2026-05-15 15:57:43 UTC

Parallelism

89/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,782,813  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x969f2d28…4fa2

0x0555e3…2b9c

2 touches
0 conflicts

0x263be3d1…19f7

0x065c9d…c394

2 touches
0 conflicts

0xf3d7a307…4d63

0x065c9d…c394

2 touches
0 conflicts

0xfe2bac2b…2cec

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity