← previous blocknext block →recent activity

Analyzing

Block #75,262,613

20 transactions · 18 stateful · 2026-05-17 21:21:43 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1.65

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,262,613  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x21d22421…0b7a

0x34b655…2a6f

8 touches
6 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xd22ea551…208d

0x065c9d…c394

5 touches
3 conflicts

0xded5ec0c…f0fc

0x34b655…2a6f

4 touches
2 conflicts

0x8cc18498…ce7e

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity