← previous blocknext block →recent activity

Analyzing

Block #74,766,917

13 transactions · 11 stateful · 2026-05-15 14:11:24 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,766,917  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x8f375dda…1b11

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

4 touches
1 conflict

0xcf17589f…048c

0x34b655…2a6f

4 touches
1 conflict

0x86644f36…7068

0x000000…012a

2 touches
0 conflicts

0xe069120c…952c

0x000000…012a

2 touches
0 conflicts

0x8fa7a69c…8fd7

0x2f6a6c…7777

2 touches
0 conflicts

0xb3f28385…15a5

0x2f6a6c…7777

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: Perpl

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity