← previous blocknext block →recent activity

Analyzing

Block #117,049,581

19 transactions · 19 stateful · 2026-10-27 13:09:09 UTC

Parallelism

63/100

Blocked

42%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #117,049,581  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf5dc501b…831c

0x34b655…2a6f

4 touches
1 conflict

0x77ef9f98…e4f4

0x34b655…2a6f

3 touches
1 conflict

0x08eb7666…9364

0x34b655…2a6f

2 touches
0 conflicts

0x09693775…7635

0x34b655…2a6f

2 touches
0 conflicts

0x24f03b2b…9aa3

0x34b655…2a6f

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)

21 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity