← previous blocknext block →recent activity

Analyzing

Block #74,948,802

16 transactions · 15 stateful · 2026-05-16 10:25:21 UTC

Parallelism

38/100

Blocked

67%

Avg conflicts / tx

2.63

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,948,802  ·  16 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

18 touches
36 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

12 touches
15 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0x90687d94…b524

0x34b655…2a6f

7 touches
6 conflicts

0x6a15f784…10b2

0x34b655…2a6f

4 touches
1 conflict

0x8a5efe9a…fa31

0x34b655…2a6f

4 touches
1 conflict

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity