← previous blocknext block →recent activity
Analyzing
Block #74,429,717
10 transactions · 8 stateful · 2026-05-14 00:36:26 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,429,717 · 10 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
2w03w17w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xa678cb89…4abd
0x34b655…2a6f
4 touches
1 conflict
0x2906176a…85b6
0x34b655…2a6f
4 touches
1 conflict
0x1ccbecde…b893
0x34b655…2a6f
2 touches
0 conflicts
0x25e86458…ac1f
0x34b655…2a6f
2 touches
0 conflicts
0x6637e421…af93
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity