← previous blocknext block →recent activity
Analyzing
Block #74,266,294
13 transactions · 12 stateful · 2026-05-13 06:29:06 UTC
Parallelism
31/100
Blocked
67%
Avg conflicts / tx
2.77
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,266,294 · 13 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
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9e70c2e…8e50
0x80f006…d585
18 touches
36 conflicts
0xe9e70c2e…8e51
0x80f006…d585
18 touches
36 conflicts
0x8f478f26…9d56
0x000000…012a
18 touches
36 conflicts
0x00000000…003a
0x54fc07…e57e
18 touches
36 conflicts
0x89bed737…29fa
0x57ea24…2cec
2 touches
0 conflicts
0x15e0ecec…e314
0x80f006…d585
2 touches
0 conflicts
0x189320de…705f
0x80f006…d585
2 touches
0 conflicts
0x27324365…8330
0x80f006…d585
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: 0x80f00661…45d585
36 conflicts on slot 0xe9e70c2e01…648e50
Audit this contract →
← previous block·next block →recent activity