← previous blocknext block →recent activity

Analyzing

Block #73,987,058

13 transactions · 11 stateful · 2026-05-11 23:30:09 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,987,058  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xefd39d1e…d732

0x34b655…2a6f

4 touches
1 conflict

0x02d67723…1743

0x34b655…2a6f

4 touches
1 conflict

0x192cb36c…648d

0x34b655…2a6f

4 touches
1 conflict

0x37276d6c…ca84

0x34b655…2a6f

4 touches
1 conflict

0x5138188e…796b

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

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

1 conflict on slot 0xefd39d1e3d…d9d732

← previous block·next block →recent activity