← previous blocknext block →recent activity

Analyzing

Block #101,250,382

16 transactions · 12 stateful · 2026-09-02 05:56:12 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,250,382  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe97d54c5…ef6f

0x34b655…2a6f

4 touches
1 conflict

0xf98c943e…7c44

0x34b655…2a6f

4 touches
1 conflict

0x00f6a8a7…0e6e

0x34b655…2a6f

4 touches
1 conflict

0x1c1d4faf…d4fb

0x34b655…2a6f

4 touches
1 conflict

0x2b43dd7d…7f99

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4b24225e…5a6b

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