← previous blocknext block →recent activity

Analyzing

Block #72,300,894

9 transactions · 7 stateful · 2026-05-04 04:06:55 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,300,894  ·  9 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

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x21756df9…567d

0x34b655…2a6f

4 touches
1 conflict

0x1e0e68f7…e4f6

0x34b655…2a6f

2 touches
0 conflicts

0x323c931a…a50c

0x34b655…2a6f

2 touches
0 conflicts

0x350f130e…902f

0x34b655…2a6f

2 touches
0 conflicts

0x3c843f4c…3a56

0x34b655…2a6f

2 touches
0 conflicts

0x4769691c…a148

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: 0x34b6552d…112a6f

1 conflict on slot 0x2484cc159b…175afc

← previous block·next block →recent activity