← previous blocknext block →recent activity

Analyzing

Block #92,048,010

14 transactions · 13 stateful · 2026-07-31 23:32:23 UTC

Parallelism

86/100

Blocked

15%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,048,010  ·  14 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

0x4c6b5b0c…4c93

0x7b9256…1fb2

4 touches
1 conflict

0x1584c0cc…c6f8

0x7b9256…1fb2

4 touches
1 conflict

0x1584c0cc…c6f9

0x7b9256…1fb2

4 touches
1 conflict

0x1584c0cc…c6fc

0x7b9256…1fb2

4 touches
1 conflict

0x4c6b5b0c…4c92

0x7b9256…1fb2

4 touches
1 conflict

0x0c15f714…46ab

0x34b655…2a6f

4 touches
1 conflict

0x5f72d58f…c445

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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: 0x7b9256fd…e21fb2

1 conflict on slot 0x4c6b5b0c6d…654c93

← previous block·next block →recent activity