← previous blocknext block →recent activity

Analyzing

Block #74,596,545

29 transactions · 23 stateful · 2026-05-14 19:13:44 UTC

Parallelism

72/100

Blocked

57%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,596,545  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x7f38bfbc…61e3

0x34b655…2a6f

8 touches
6 conflicts

0xca0fef1c…b548

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

6 touches
3 conflicts

0x9d1bb389…c7d9

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity