← previous blocknext block →recent activity

Analyzing

Block #99,284,426

16 transactions · 16 stateful · 2026-08-26 08:44:25 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #99,284,426  ·  16 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

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x0dd3d3cd…7281

0x34b655…2a6f

4 touches
1 conflict

0x23769ebc…c8ed

0x34b655…2a6f

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0x3f3d3cdb…9d30

0x34b655…2a6f

4 touches
1 conflict

0x4188cc5f…2d2e

0x34b655…2a6f

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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: USDC (USDC)

1 conflict on slot 0xd17580f913…78ece1

← previous block·next block →recent activity