← previous blocknext block →recent activity

Analyzing

Block #72,097,840

16 transactions · 14 stateful · 2026-05-03 05:27:04 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,097,840  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x7e9d3a…9fda

14 touches
21 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x1d515643…99ba

0x34b655…2a6f

2 touches
0 conflicts

0x239b9992…4977

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x26bbcb47…263f

0x34b655…2a6f

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: 0x7e9d3a8a…4f9fda

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity