← previous blocknext block →recent activity
Analyzing
Block #74,428,804
14 transactions · 13 stateful · 2026-05-14 00:30:21 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,428,804 · 14 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
3w04w15w06w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x0fb5a577…7bad
0x34b655…2a6f
2 touches
0 conflicts
0x36f4b4f0…0188
0x34b655…2a6f
2 touches
0 conflicts
0x46356904…5ead
0x34b655…2a6f
2 touches
0 conflicts
0x6e0198ee…ebe1
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: Perpl
1 conflict on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity