← previous blocknext block →recent activity

Analyzing

Block #74,285,679

15 transactions · 13 stateful · 2026-05-13 08:38:00 UTC

Parallelism

60/100

Blocked

46%

Avg conflicts / tx

1.07

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,285,679  ·  15 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

0x7b7bcac3…8fbf

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xbb12db23…857e

0x34b655…2a6f

8 touches
6 conflicts

0x88ddd628…7d59

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xc12b04b0…884b

0x34b655…2a6f

6 touches
3 conflicts

0x7ce50268…4fbf

0x34b655…2a6f

6 touches
3 conflicts

0x5aed1bd2…7afa

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: 0x34b6552d…112a6f

15 conflicts on slot 0x7b7bcac3fe…968fbf

← previous block·next block →recent activity