← previous blocknext block →recent activity
Analyzing
Block #74,429,503
16 transactions · 13 stateful · 2026-05-14 00:35:00 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,429,503 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w18w09w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x3e4b8d9f…b8a7
0x5d823e…89c6
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf0f673fd…37a7
0x5d823e…89c6
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x2e2214a9…fe0d
0x5d823e…89c6
4 touches
1 conflict
0xbbee74c2…567a
0x065c9d…c394
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity