← previous blocknext block →recent activity

Analyzing

Block #74,450,848

18 transactions · 11 stateful · 2026-05-14 02:57:07 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,450,848  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x6fb3fdf1…45b3

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x63d7ebf0…3dd9

0x34b655…2a6f

4 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

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

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity