← previous blocknext block →recent activity

Analyzing

Block #75,543,467

14 transactions · 13 stateful · 2026-05-19 04:46:43 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,543,467  ·  14 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

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

0xf0a7ca33…3c7e

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0x12bc0d2c…1c12

0x34b655…2a6f

4 touches
1 conflict

0x8cf3d245…1d0d

0x1d1325…2305

2 touches
0 conflicts

0xad3ef711…4f2b

0x1d1325…2305

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 0x23a320fbfb…26cbd7

← previous block·next block →recent activity