← previous blocknext block →recent activity

Analyzing

Block #74,215,256

15 transactions · 13 stateful · 2026-05-13 00:49:48 UTC

Parallelism

53/100

Blocked

62%

Avg conflicts / tx

1.47

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,215,256  ·  15 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfd784183…67bb

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

6 touches
3 conflicts

0xa8ddf3d3…ece4

0x34b655…2a6f

6 touches
3 conflicts

0xe6bc2705…d15b

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

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