← previous blocknext block →recent activity

Analyzing

Block #116,889,503

21 transactions · 21 stateful · 2026-10-26 23:42:20 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #116,889,503  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x5ee3f950…32bf

0x264123…670e

4 touches
1 conflict

0xab07df27…2647

0x264123…670e

4 touches
1 conflict

0xc2575a0e…f805

0xc9de99…405d

4 touches
1 conflict

0xc2575a0e…f92b

0xc9de99…405d

4 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x09000000…0007

0x000000…1000

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity