← previous blocknext block →recent activity

Analyzing

Block #74,645,887

16 transactions · 11 stateful · 2026-05-15 00:43:13 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,645,887  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x309ef367…e8a1

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x23506d63…0127

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x775a5910…3fa3

0x065c9d…c394

2 touches
0 conflicts

0xa54172f4…6d16

0x065c9d…c394

2 touches
0 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

1 conflict on slot 0x070a562acf…648147

← previous block·next block →recent activity