← previous blocknext block →recent activity
Analyzing
Block #74,223,330
23 transactions · 20 stateful · 2026-05-13 01:43:34 UTC
Parallelism
78/100
Blocked
30%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,223,330 · 23 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
1w02w110w113w014w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
10 touches
10 conflicts
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 conflicts
0x73f4551d…4188
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x910ae0a0…c239
0x34b655…2a6f
4 touches
1 conflict
0xa26c29a3…c434
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
10 conflicts on slot 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity