← previous blocknext block →recent activity

Analyzing

Block #73,696,152

15 transactions · 13 stateful · 2026-05-10 15:02:28 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,696,152  ·  15 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

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe8eb406c…08ae

0xa6afd3…d132

4 touches
1 conflict

0x8f375dda…1b11

0x34b655…2a6f

4 touches
1 conflict

0x11b69a7e…334e

0xee8c0e…1242

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0x09000000…0001

0x000000…1000

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: 0x681e908b…e1ae09

3 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity