← previous blocknext block →recent activity
Analyzing
Block #74,335,956
15 transactions · 13 stateful · 2026-05-13 14:12:29 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,335,956 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a6a2a1a…c177
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xf3981be5…2c47
0x34b655…2a6f
4 touches
1 conflict
0x98b3db47…a83f
0x350035…7777
2 touches
1 conflict
0x04c00b0b…d324
0x065c9d…c394
2 touches
0 conflicts
0x0ed87692…8bcc
0x065c9d…c394
2 touches
0 conflicts
0x1eab66ca…c577
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
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: Perpl
1 conflict on slot 0x4a6a2a1a2e…f6c177
Audit this contract →
← previous block·next block →recent activity