← previous blocknext block →recent activity

Analyzing

Block #102,220,458

19 transactions · 19 stateful · 2026-09-05 15:29:15 UTC

Parallelism

89/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,220,458  ·  19 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

0x75d12995…42e0

0x34b655…2a6f

4 touches
1 conflict

0x921a58d1…db22

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc852b267…9d14

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc5f

0x34b655…2a6f

4 touches
1 conflict

0xf63c2a2b…bc60

0x34b655…2a6f

4 touches
1 conflict

0xfe45073e…6315

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