← previous blocknext block →recent activity

Analyzing

Block #100,247,539

16 transactions · 13 stateful · 2026-08-29 17:47:17 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,247,539  ·  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

0x2ef1d89b…196d

0x754704…b603

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x537b38ff…2c21

0x34b655…2a6f

4 touches
1 conflict

0x74e485b1…d380

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6426

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0036

0x35a73b…6042

4 touches
1 conflict

0xaf831072…51d5

0x69a5f9…2fef

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 0x2ef1d89b7e…45196d

← previous block·next block →recent activity