← previous blocknext block →recent activity
Analyzing
Block #74,912,251
9 transactions · 7 stateful · 2026-05-16 06:21:03 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,912,251 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x0e291d91…2633
0x065c9d…c394
2 touches
0 conflicts
0x6e533234…30a9
0x065c9d…c394
2 touches
0 conflicts
0xaa7f89e2…5a4c
0x065c9d…c394
2 touches
0 conflicts
0xac8b4bce…8ca6
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
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 0x97b0b2ee68…854666
Audit this contract →
← previous block·next block →recent activity