← previous blocknext block →recent activity

Analyzing

Block #101,681,773

20 transactions · 18 stateful · 2026-09-03 18:06:41 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1.3

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #101,681,773  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xaa3b4402…74e6

0x34b655…2a6f

6 touches
3 conflicts

0x733c7779…a647

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x24f02a95…e71b

0x34b655…2a6f

4 touches
1 conflict

0x2592310e…03a5

0x34b655…2a6f

4 touches
1 conflict

0x70f836c8…cf6d

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: Perpl

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity