← previous blocknext block →recent activity

Analyzing

Block #75,543,447

12 transactions · 11 stateful · 2026-05-19 04:46:35 UTC

Parallelism

58/100

Blocked

55%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,543,447  ·  12 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0x99a21305…dffc

0x2a68ba…90c5

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x385efb7e…f7eb

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x3cf5ed4a…c35d

0x34b655…2a6f

4 touches
1 conflict

0x309ef367…e8a1

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity