← previous blocknext block →recent activity

Analyzing

Block #84,073,654

20 transactions · 17 stateful · 2026-06-27 17:04:41 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #84,073,654  ·  20 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

0x00000000…0002

0xd637b3…4160

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x32359294…7113

0x34b655…2a6f

4 touches
1 conflict

0x9863393c…ce7b

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

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: 0xd637b38f…c64160

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity