← previous blocknext block →recent activity

Analyzing

Block #93,500,183

17 transactions · 16 stateful · 2026-08-06 01:18:30 UTC

Parallelism

88/100

Blocked

25%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,500,183  ·  17 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

0xd379a368…fea4

0x34b655…2a6f

4 touches
1 conflict

0xf931da26…5178

0x34b655…2a6f

4 touches
1 conflict

0x1c795b3a…8e8a

0x754704…b603

4 touches
1 conflict

0x3a473699…6159

0x754704…b603

4 touches
1 conflict

0x8434d4d0…d5d8

0x754704…b603

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xbe9c752a…5271

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

1 conflict on slot 0xd379a36873…4efea4

← previous block·next block →recent activity