← previous blocknext block →recent activity

Analyzing

Block #74,484,284

21 transactions · 18 stateful · 2026-05-14 06:39:38 UTC

Parallelism

52/100

Blocked

50%

Avg conflicts / tx

2.14

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,484,284  ·  21 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x293e2f…13a7

20 touches
45 conflicts

0xc27346d4…90a3

0x9c82eb…cd90

20 touches
45 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00397cf6…cdad

0x293e2f…13a7

2 touches
0 conflicts

0x0a987a4f…8cb5

0x293e2f…13a7

2 touches
0 conflicts

0x0d249e95…94ca

0x293e2f…13a7

2 touches
0 conflicts

0x10960bcd…5524

0x293e2f…13a7

2 touches
0 conflicts

0x3eaf6bf5…b90e

0x293e2f…13a7

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: 0x293e2f01…5113a7

45 conflicts on slot 0x0000000000…000036

← previous block·next block →recent activity