← previous blocknext block →recent activity
Analyzing
Block #74,901,366
30 transactions · 22 stateful · 2026-05-16 05:08:29 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,901,366 · 30 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
1w03w16w27w19w010w111w225w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fc6ea79…e2dc
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x5c6af4a8…6ece
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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 0x9fc6ea791d…ace2dc
Audit this contract →
← previous block·next block →recent activity