← previous blocknext block →recent activity

Analyzing

Block #83,639,556

23 transactions · 20 stateful · 2026-06-25 16:50:12 UTC

Parallelism

70/100

Blocked

55%

Avg conflicts / tx

1.17

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,639,556  ·  23 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

0x00000000…0002

0xaa7ee7…f0e4

14 touches
21 conflicts

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x75291f8b…3ac0

0x34b655…2a6f

4 touches
1 conflict

0x8f0e8a2f…a850

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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: 0xaa7ee7ce…aff0e4

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity