← previous blocknext block →recent activity

Analyzing

Block #74,340,740

28 transactions · 22 stateful · 2026-05-13 14:44:20 UTC

Parallelism

79/100

Blocked

64%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,340,740  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x90a6030d…08e3

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…000b

0x5d823e…89c6

6 touches
3 conflicts

0x0175b7a6…1db9

0x5d823e…89c6

6 touches
3 conflicts

0x0175b7a6…1dba

0x5d823e…89c6

6 touches
3 conflicts

0x0175b7a6…1dbb

0x5d823e…89c6

6 touches
3 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

6 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity