← previous blocknext block →recent activity

Analyzing

Block #75,070,147

23 transactions · 20 stateful · 2026-05-16 23:56:19 UTC

Parallelism

39/100

Blocked

65%

Avg conflicts / tx

3.96

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #75,070,147  ·  23 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xa164d951…1534

0xe1c8b7…3022

28 touches
91 conflicts

0x67d846dd…358c

0xcf23a0…7777

28 touches
91 conflicts

0x44ed742f…63f5

0x3bd359…433a

28 touches
91 conflicts

0x4eb758b8…b13b

0x3bd359…433a

28 touches
91 conflicts

0x10ef7671…aedb

0x9f3832…4ae4

28 touches
91 conflicts

0x7cf5136f…ba69

0x9f3832…4ae4

28 touches
91 conflicts

0xabfc8d98…bbe5

0x9f3832…4ae4

28 touches
91 conflicts

0xabfc8d98…bbe6

0x9f3832…4ae4

28 touches
91 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: 0xe1c8b733…e33022

91 conflicts on slot 0xa164d95170…fa1534

← previous block·next block →recent activity