← previous blocknext block →recent activity
Analyzing
Block #74,461,075
22 transactions · 18 stateful · 2026-05-14 04:05:14 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,461,075 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w08w19w210w313w114w015w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x1da1c6cb…bb3f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x10814d14…cdda
0x34b655…2a6f
4 touches
1 conflict
0x22b30b22…5410
0x34b655…2a6f
4 touches
1 conflict
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity