← previous blocknext block →recent activity
Analyzing
Block #74,258,908
14 transactions · 14 stateful · 2026-05-13 05:40:01 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,258,908 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w17w28w111w112w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a0d91a0…2b15
0x34b655…2a6f
8 touches
6 conflicts
0x6d6a73bb…a2f9
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0xeb0915f1…c150
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x20ac0567…c954
0x34b655…2a6f
6 touches
3 conflicts
0x2484cc15…5afc
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0x8a0d91a0f4…862b15
Audit this contract →
← previous block·next block →recent activity