← previous blocknext block →recent activity

Analyzing

Block #74,650,783

30 transactions · 28 stateful · 2026-05-15 01:15:45 UTC

Parallelism

33/100

Blocked

71%

Avg conflicts / tx

6.37

Longest chain

20 deep

Execution timeline

did this block parallelize well?

view

block #74,650,783  ·  30 txs across 20 waves  ·  depth 20
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

wave w14

wave w15

wave w16

wave w17

wave w18

wave w19

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

0xc701ef68…587b

0x3bd359…433a

40 touches
190 conflicts

0x00000000…0000

0x97805d…bb07

40 touches
190 conflicts

0x00000000…0001

0x97805d…bb07

40 touches
190 conflicts

0x00000000…0003

0x97805d…bb07

40 touches
190 conflicts

0xf9da2e00…a63d

0xe9afa1…7777

40 touches
190 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x09000000…0001

0x000000…1000

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: 0x3bd359c1…15433a

190 conflicts on slot 0xc701ef68af…44587b

← previous block·next block →recent activity