← previous blocknext block →recent activity

Analyzing

Block #74,483,020

27 transactions · 21 stateful · 2026-05-14 06:31:12 UTC

Parallelism

67/100

Blocked

62%

Avg conflicts / tx

1.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,483,020  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

16 touches
28 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xef184a54…5801

0x34b655…2a6f

6 touches
3 conflicts

0xd895ee0b…d301

0x34b655…2a6f

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity