← previous blocknext block →recent activity

Analyzing

Block #74,183,684

22 transactions · 18 stateful · 2026-05-12 21:19:52 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,183,684  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0003

0x579d00…83f8

14 touches
21 conflicts

0x00000000…0002

0x579d00…83f8

14 touches
21 conflicts

0x00000000…0000

0x579d00…83f8

14 touches
21 conflicts

0xb4b3c404…f0aa

0x3bd359…433a

14 touches
21 conflicts

0x399cd013…b14f

0x23ae8c…7777

14 touches
21 conflicts

0x768cffcd…2648

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 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: 0x579d005c…ab83f8

21 conflicts on slot 0x0000000000…000003

← previous block·next block →recent activity