← previous blocknext block →recent activity
Analyzing
Block #74,228,984
10 transactions · 9 stateful · 2026-05-13 02:21:05 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,228,984 · 10 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
1w02w14w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x26867cdc…dab5
0x34b655…2a6f
2 touches
0 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
2 touches
0 conflicts
0x41629728…ee69
0x34b655…2a6f
2 touches
0 conflicts
0x46d1e316…a1e1
0x34b655…2a6f
2 touches
0 conflicts
0x4ad5c8b3…dea2
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