← previous blocknext block →recent activity

Analyzing

Block #73,869,064

19 transactions · 12 stateful · 2026-05-11 10:23:37 UTC

Parallelism

68/100

Blocked

42%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,869,064  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0007

0x1414f3…5137

12 touches
15 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x3edc0cad…3803

0x1414f3…5137

2 touches
0 conflicts

0x80d8b017…ce61

0x1414f3…5137

2 touches
0 conflicts

0x8ccfea1c…7c5c

0x1414f3…5137

2 touches
0 conflicts

0xa25fd703…fde1

0x1414f3…5137

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

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: 0x1414f3ba…045137

15 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity