← previous blocknext block →recent activity

Analyzing

Block #74,234,400

15 transactions · 13 stateful · 2026-05-13 02:57:08 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,234,400  ·  15 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

0x768cffcd…2648

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xc12b04b0…884b

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x1b159f3d…9163

0x34b655…2a6f

4 touches
1 conflict

0x1fd20d14…80dd

0x34b655…2a6f

4 touches
1 conflict

0x71e96b74…abe9

0x34b655…2a6f

4 touches
1 conflict

0xa26c29a3…c434

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

10 conflicts on slot 0x768cffcdb0…d12648

← previous block·next block →recent activity