← previous blocknext block →recent activity

Analyzing

Block #75,598,093

22 transactions · 15 stateful · 2026-05-19 10:50:27 UTC

Parallelism

82/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,598,093  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x676958f8…e4bb

0xd32edf…ff58

7 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x74749e85…1dc6

0x065c9d…c394

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0003

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0009

0x04ddf6…7f33

2 touches
0 conflicts

0x3eac71be…e886

0x0a3323…0a3c

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: 0xd32edf66…9fff58

6 conflicts on slot 0x676958f80b…a0e4bb

← previous block·next block →recent activity