← previous blocknext block →recent activity

Analyzing

Block #74,631,131

14 transactions · 13 stateful · 2026-05-14 23:04:55 UTC

Parallelism

57/100

Blocked

46%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,631,131  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xab3526…fa38

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x1c9e5f70…b1c1

0x09475a…400f

2 touches
0 conflicts

0x389b4774…456b

0x09475a…400f

2 touches
0 conflicts

0x5cff04de…966b

0x09475a…400f

2 touches
0 conflicts

0xa4a25f66…0f1e

0x09475a…400f

2 touches
0 conflicts

0xafb857af…666b

0x09475a…400f

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity