← previous blocknext block →recent activity

Analyzing

Block #74,335,874

6 transactions · 6 stateful · 2026-05-13 14:11:56 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,335,874  ·  6 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

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0xa9d9912c…75a7

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

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

1 conflict on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity