← previous blocknext block →recent activity

Analyzing

Block #75,087,813

13 transactions · 11 stateful · 2026-05-17 01:54:30 UTC

Parallelism

54/100

Blocked

55%

Avg conflicts / tx

1.23

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,087,813  ·  13 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

0x5e24c5e6…330d

0x754704…b603

12 touches
15 conflicts

0xc4e19ae4…0788

0xe7cd86…c82d

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x0e2d9e1a…65d6

0x754704…b603

2 touches
0 conflicts

0x2fae659b…7fb9

0x754704…b603

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x754704bc…afb603

15 conflicts on slot 0x5e24c5e63c…91330d

← previous block·next block →recent activity