← previous blocknext block →recent activity

Analyzing

Block #73,695,019

11 transactions · 10 stateful · 2026-05-10 14:54:51 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,695,019  ·  11 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x1aba5fe2…62f4

0x065c9d…c394

4 touches
1 conflict

0x3e733ae4…4598

0x34b655…2a6f

4 touches
1 conflict

0xb07ca832…5f01

0x065c9d…c394

2 touches
0 conflicts

0xb17d566b…fd21

0x065c9d…c394

2 touches
0 conflicts

0xbc85747a…a1c0

0x065c9d…c394

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity