← previous blocknext block →recent activity

Analyzing

Block #102,216,058

15 transactions · 14 stateful · 2026-09-05 15:07:04 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,216,058  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x02372d42…1871

0x34b655…2a6f

4 touches
1 conflict

0x0ec07cf7…c0c9

0x34b655…2a6f

4 touches
1 conflict

0x1244b105…8e9b

0x34b655…2a6f

4 touches
1 conflict

0x1ad1b24f…c6ce

0x34b655…2a6f

4 touches
1 conflict

0x24b08f9c…e594

0x34b655…2a6f

4 touches
1 conflict

0x3027f5b0…7a3f

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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity