← previous blocknext block →recent activity

Analyzing

Block #90,786,950

23 transactions · 20 stateful · 2026-07-27 13:45:06 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,786,950  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0002

0x48cba2…b48b

6 touches
3 conflicts

0x92a5eb10…d5e3

0x34b655…2a6f

6 touches
3 conflicts

0xf484cb8d…5dbb

0x34b655…2a6f

6 touches
3 conflicts

0x36b1d1cd…4009

0x34b655…2a6f

4 touches
1 conflict

0x6b2ba712…0214

0x34b655…2a6f

4 touches
1 conflict

0x6c7cb3c8…71da

0x34b655…2a6f

4 touches
1 conflict

0x7485bb0e…d1e0

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: Perpl

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity