← previous blocknext block →recent activity

Analyzing

Block #72,094,365

26 transactions · 20 stateful · 2026-05-03 05:03:56 UTC

Parallelism

65/100

Blocked

65%

Avg conflicts / tx

1.62

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,094,365  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

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

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity