← previous blocknext block →recent activity

Analyzing

Block #73,859,713

6 transactions · 5 stateful · 2026-05-11 09:21:15 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,859,713  ·  6 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

0x00000000…00fc

0xd45826…f134

4 touches
1 conflict

0x00000000…0161

0xd45826…f134

4 touches
1 conflict

0x8ebf69ec…edcd

0xd45826…f134

4 touches
1 conflict

0x8ebf69ec…edd2

0xd45826…f134

4 touches
1 conflict

0x6aa00a00…64c4

0x1308d7…ff6c

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

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: 0xd458261e…e6f134

1 conflict on slot 0x0000000000…0000fc

← previous block·next block →recent activity