← previous blocknext block →recent activity
Analyzing
Block #74,432,663
18 transactions · 16 stateful · 2026-05-14 00:56:08 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,432,663 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x06b3fede…7ccc
0x34b655…2a6f
2 touches
0 conflicts
0x12ac24a4…630c
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x3b2d25d4…fb40
0x34b655…2a6f
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: 0xab35264b…1cfa38
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity