← previous blocknext block →recent activity

Analyzing

Block #96,030,204

19 transactions · 19 stateful · 2026-08-14 21:56:39 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

2.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #96,030,204  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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…0031

0x59df86…2780

18 touches
36 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd29144b1…30b5

0x34b655…2a6f

4 touches
1 conflict

0x833f3561…bfd0

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

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: 0x59df8637…6d2780

36 conflicts on slot 0x0000000000…000031

← previous block·next block →recent activity