← previous blocknext block →recent activity

Analyzing

Block #101,313,862

22 transactions · 22 stateful · 2026-09-02 11:15:37 UTC

Parallelism

59/100

Blocked

41%

Avg conflicts / tx

1.68

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #101,313,862  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xabde8104…c9a9

0x2a68ba…90c5

2 touches
0 conflicts

0x10abefc9…c9bc

0x34ae4d…3fc5

2 touches
0 conflicts

0x10d80fee…dbda

0x34ae4d…3fc5

2 touches
0 conflicts

0x40970e69…da50

0x34ae4d…3fc5

2 touches
0 conflicts

0x8cf3d245…1d0d

0x34ae4d…3fc5

2 touches
0 conflicts

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)

36 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity